What it is

AWS Verified Access is a zero trust access service. Users reach internal web (and, more recently, non-HTTP) applications without a VPN after Verified Access checks who the user is and the state of their device against policy for each request.

How it works

  1. A user requests an application through a Verified Access endpoint.
  2. Verified Access evaluates the request against trust providers:
    • User identity provider: AWS IAM Identity Center or an OIDC provider.
    • Device provider: a device management product such as Jamf, CrowdStrike or JumpCloud.
  3. A policy written in Cedar decides allow or deny. For example: allow if the user belongs to the finance group, and the device is managed and compliant.
  4. If allowed, traffic is forwarded to the application in your VPC.

Building blocks

Why use it

Verified Access vs Client VPN

Client VPN gives a user a network path. Verified Access gives a user a single authorized application path. For most web-based corporate applications Verified Access reduces the blast radius of a compromised user.

Watch-outs

Quotas, limits and pricing change often. Confirm current values in the AWS documentation before designing around them.