AWS Verified Access cost: per app connection per hour plus data
Verified Access bills per application connected per hour plus data processed, giving zero-trust access to internal apps without a VPN. Many connected apps and high traffic drive the bill. Here is the model.
Quick answer
AWS Verified Access bills per application connected per hour plus per GB of data processed, providing zero-trust access to internal applications without a VPN. Cost scales with how many applications you connect and how much traffic flows, so connecting only the applications that need it and being aware of the per-app hourly charge are the levers. It replaces VPN cost and operational burden with per-app pricing.
AWS Verified Access provides secure, zero-trust access to internal applications without a VPN, evaluating identity and device posture on every request. It is priced per application connection per hour plus data processed, so cost tracks how many applications you put behind it and how much traffic they serve.
Per app-hour plus data
| Dimension | Bills for |
|---|---|
| Application connection | Per application, per hour connected |
| Data processed | Per GB of traffic through Verified Access |
Each application you connect to Verified Access bills per hour it is connected, whether or not it is actively used, plus a per-gigabyte charge on the data processed. So the app-hour cost scales with the number of applications, and the data cost with traffic. An organization exposing many internal applications this way accumulates per-app hourly charges.
Versus a VPN
Verified Access replaces the cost and operational burden of running VPN infrastructure (client management, gateway capacity, the coarse network-level access a VPN grants) with per-application, per-request zero-trust access. So the comparison is not just price but security model: Verified Access grants access per application with identity and device checks, which a VPN does not. For organizations moving to zero-trust, the per-app cost buys a better model.
Controlling Verified Access cost
Connect only the applications that genuinely need this access model rather than everything, be aware that each connected application bills hourly whether or not used (so disconnect applications you no longer expose), and account for the data-processing charge on high-traffic applications. The per-app hourly billing rewards keeping the set of connected applications tight, the same right-size discipline as any per-resource-hour service.
FAQ
How is AWS Verified Access priced?
Per application connected per hour, plus per GB of data processed through it. It provides zero-trust access to internal applications without a VPN. Cost scales with how many applications you connect (each billing hourly whether or not used) and how much traffic flows through them.
How do I reduce Verified Access cost?
Connect only the applications that genuinely need this zero-trust access model rather than everything, disconnect applications you no longer expose (each connected app bills hourly whether or not used), and account for the data-processing charge on high-traffic applications. Keeping the set of connected applications tight is the main lever.
Is Verified Access cheaper than a VPN?
It depends on scale, but the comparison is about the security model, not just price. Verified Access grants per-application access with identity and device checks and removes VPN operational burden (client management, gateway capacity), while a VPN grants coarser network-level access. For organizations moving to zero-trust, the per-app cost buys a better model.
Does Verified Access charge for idle applications?
Yes. Each connected application bills per hour it is connected, whether or not it is actively used. So disconnecting applications you no longer expose stops their hourly charge. The per-app hourly billing rewards keeping the set of connected applications limited to those that need the access.
What drives Verified Access cost?
The number of connected applications (each billing per hour) and the traffic volume (billed per GB processed). An organization exposing many internal applications accumulates per-app hourly charges, and high-traffic applications add data-processing cost. Both scale the bill, so scoping connected apps and being aware of data charges are the levers.
Does C3X estimate Verified Access cost?
C3X prices the Verified Access resources from your Terraform, including the per-application hourly component, so the connection cost appears before deploy. Data-processing cost depends on traffic volume, which you provide as a usage assumption.
What to do next
Estimate your zero-trust access cost before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.