AWS Verified Access
aws.amazon.com
- Windows
- macOS
- Linux
- Web
- API
What AWS Verified Access is
AWS Verified Access provides access to corporate applications and resources without a VPN. It evaluates every application request against access policies and trust data from selected AWS or third-party providers; requests are denied by default until an administrator defines a policy. Policies can consider user identity and device security state, with device management integrations supplying context about security and compliance. The service supports HTTP(S) and TCP applications, as well as access to AWS infrastructure resources such as EC2 instances through specified IP addresses and port ranges. For secured non-HTTP(S) applications, users can connect with the desktop Connectivity Client, available for Windows Intel and macOS on Apple silicon or Intel. Administrators can use the AWS Management Console, CLI, SDKs, or Query API. Access attempts can be sent to Amazon S3, CloudWatch Logs, or Kinesis Data Firehose, with OCSF format support. Traffic from end users to endpoints over the internet is encrypted with TLS 1.2 or later. AWS secures the cloud infrastructure; customers remain responsible for security in the cloud and their configurations.
Who it suits
It suits IT administrators providing access to corporate applications and infrastructure for remote employees or external contractors. Device management integrations can provide security and compliance context for access policies.
Good to know, and what to watch
- Supports HTTP(S) and TCP applications
- Policies can use identity and device security state
- Access logs can be delivered to three AWS services
- Encrypts internet traffic to endpoints with TLS 1.2 or later
- Requests are denied until an access policy is defined
- No free plan is listed
- Customers remain responsible for in-cloud security and configuration
- Application and endpoint usage is billed by time
Plans
Every plan and priceConnectivity Client
Non-HTTP(S) applications
HTTP(S) applications
Getting started
- Open the AWS Verified Access website and AWS Management Console
- Choose an AWS or third-party trust provider
- Define an access policy before allowing requests
- Configure HTTP(S), TCP, or AWS infrastructure resources
- Install the Connectivity Client for secured non-HTTP(S) applications
- Send access logs to S3, CloudWatch Logs, or Kinesis Data Firehose
Limits to check
The service has no free plan. Example pricing includes $0.20 per non-HTTP(S) endpoint-hour and $0.27 per HTTP(S) application-hour in US East, with connection, tier, and data-processing charges also applying.
The verdict
Verified Access can apply identity and device context to requests for corporate applications and infrastructure, with logging and administrator interfaces across AWS tools. Customers need to define policies and manage their own in-cloud security and configuration.
Questions people ask
Does AWS Verified Access require a VPN?
No. It provides access to corporate applications and resources without a VPN.
Which applications and protocols are supported?
It supports HTTP(S) and TCP applications, plus SSH, RDP, and AWS infrastructure resources such as EC2 over specified IP addresses and port ranges.
Is there a free plan?
No. The Connectivity Client is provided free of charge, but the service has paid usage plans.
What does the Connectivity Client support?
It is a desktop application for non-HTTP(S) applications, with Windows Intel and macOS Apple silicon or Intel downloads.
How are access attempts logged?
Logs can be delivered to Amazon S3, Amazon CloudWatch Logs, or Amazon Kinesis Data Firehose, with OCSF format support.
What identity providers can it use?
AWS IAM Identity Center supports SAML-based third-party identity providers, and Verified Access can connect directly to custom OpenID Connect-compatible providers.
What the maker publishes
- Client platforms
- The Connectivity Client is a desktop application for accessing secured non-HTTP(S) applications, with downloads listed for Windows Intel and macOS on Apple silicon or Intel. source
- Company
- Amazon Web Services says it launched in 2006. source
- Compliance responsibility
- AWS describes security as a shared responsibility, with AWS securing the cloud infrastructure and customers responsible for security in the cloud and their configurations. source
- Device posture
- Third-party device management integrations provide security context for assessing a device’s security and compliance state. source
- Encryption
- Verified Access encrypts data in transit from end users to its endpoints over the internet using TLS 1.2 or later. source
- Integrations
- AWS IAM Identity Center supports authentication through SAML-based third-party identity providers, and Verified Access can connect directly to custom OpenID Connect-compatible identity providers. source
- Intended users
- AWS describes use cases for remote employees and external contractors, as well as IT administrators securing corporate applications and infrastructure resources. source
- Interfaces
- Administrators can work with Verified Access through the AWS Management Console, AWS CLI, AWS SDKs, or Query API. source
- Logging
- It logs access attempts and can deliver logs to Amazon S3, Amazon CloudWatch Logs, and Amazon Kinesis Data Firehose, with support for the OCSF logging format. source
- Partner ecosystem
- AWS lists integrations or partnerships involving Cisco, CrowdStrike, JumpCloud, CyberArk, IBM, Datadog, JAMF, Okta, and Trellix. source
- Policy inputs
- Access policies can use factors including user identity and device security state. source
- Purpose
- AWS Verified Access provides secure access to corporate applications and resources without a VPN. source
- Request evaluation
- It evaluates every application request using trust data from a selected AWS or third-party provider and access policies, and requests are denied by default until a policy is defined. source
- Supported access
- Verified Access supports HTTP(S) applications and TCP applications, and can provide access to AWS infrastructure resources such as EC2 instances over specified IP addresses and port ranges. source
Checked against the maker's pages on 9 Oct 2026.