AWS Verified Access launches Zero Trust access to resources over non-HTTP(S) protocols

Today, AWS announces the general availability of AWS Verified Access’ support for secure access to resources that connect over protocols such as TCP, SSH, and RDP. With this launch, you can use Verified Access to provide secure VPN-less access to all your corporate applications and resources using AWS zero trust principles. This feature eliminates the need to manage separate access, and connectivity solutions for non-HTTP(S) resources on AWS and simplifies security operations.

Verified Access allows admins to set access policies based on user identity and device posture. It evaluates access for new connections and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren't met. Now you can extend your existing Verified Access policies to enable secure access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. For example, you can centrally define access policies granting prod database access only to authenticated database administrators using compliant, managed devices. This simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface.

This feature is generally available in 18 AWS regions: US East (Ohio), US East (Northern Virginia), US West (N California), US West (Oregon), Canada (Central), Asia Pacific (Sydney), Asia Pacific (Jakarta), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Milan), Europe (Stockholm), South America (São Paulo), and Israel (Tel Aviv).

To learn more, visit the product page, pricing page, and documentation.