Healthlinemags
Honest comparisons, side-by-side picks.
VPNs · en

AWS VPN gateway

By Rafael Bergstrom · · 12 min
AWS VPN gateway
AWS VPN gateway

A practical guide to AWS VPN gateway options, pricing, and setup for secure hybrid connectivity.

AWS VPN gateway: what it is and how it fits into your network

If you’re building a hybrid cloud or expanding secure remote access, an AWS VPN gateway is the essential component that bridges your on‑premises network with your AWS VPC. AWS offers a few related services under the VPN umbrella, including AWS Site-to-Site VPN, AWS Client VPN, and the newer AWS Transit Gateway with VPN capabilities. In this article, we break down what a VPN gateway is, how the main options work, pricing considerations, and best practices to help you choose the right setup for your needs.

VPN

Comparison of AWS VPN gateway options at a glance

FeatureAWS Site-to-Site VPNAWS Client VPNAWS Transit Gateway + VPNHow it works (overview)
Primary use caseSite-to-site connectivityRemote access for usersCentralized hub for many VPNsHigh-level flow
Connectivity typeIPSec VPN tunnelsOpenVPN/WireGuard over TLSVPN attachment to VPCsNetwork path
Clients supportedOn-prem devices, routersEnd users (devices)VPC attachments, other VPNsClient and network roles
Control planeAWS managedAWS managedAWS managed with TGWManagement layer
Throughput / scaleModerateUser-based sessionsLarge scale, many tunnelsCapacity concept
Redundancy / failoverYes, tunnelsYes, multiple clientsYes, TGW redundantAvailability concept
Typical use case examplesBranch office to VPCRemote workforceGlobal connectivity to many VPCsUse case category
Billing granularityPer VPN connection + dataPer connection + dataPer attachment + dataCost structure
Deployment complexityModerateLow to moderateHigherSetup effort
PrerequisitesVPN device, VPCManaged directory optionalVPCs, TGWPrereq snapshot
Best forClassic site-to-site needsSecure remote access for usersLarge, scalable networksRecommendation tag

Compiled November 2026; check the provider's site for current details.

What is a VPN gateway in AWS?

A VPN gateway is a logical and/or physical endpoint that enables encrypted connections between your own network (on-premises, data center, or branch offices) and your AWS resources inside a Virtual Private Cloud (VPC).

  • Virtual private gateway: A device on the AWS side that attaches to your VPC and terminates Site-to-Site VPN connections.
  • Customer gateway: The on‑premises device (physical or software) you manage that creates the customer end of the VPN tunnel.
  • Transit gateway: A scalable hub that interconnects VPCs and on‑premises networks, optionally hosting VPN connections for broader topologies.

In short, the AWS VPN gateway is the secure channel that carries traffic between your network and your AWS resources, with different architectural patterns depending on scale and topology.

AWS VPN gateway: Checklist

AWS Site-to-Site VPN: the classic approach

Site-to-Site VPN provides a secure IPSec tunnel between your on‑premises network and a VPC using a virtual private gateway on the AWS side and a customer gateway on your side.

Key characteristics:

  • Two VPN tunnels for resiliency: If one tunnel drops, the other can continue transporting traffic.
  • Requires configuration of route tables and security groups to ensure traffic flows to and from your VPC subnets.
  • Works with existing on‑premises hardware or software appliances that can act as a customer gateway.

How it typically works: Mac disable Edge password manager nordpass

  • You attach a virtual private gateway to your VPC.
  • You create a Site-to-Site VPN connection that defines the tunnel endpoints.
  • You configure your on‑premises customer gateway device and update routing to use the VPN connection.
  • AWS handles encryption and transport over the public internet (or via a private link if you have hybrid connectivity options).

Common questions:

  • Q: What is a VPN gateway in AWS? A: It’s the AWS-side endpoint (virtual private gateway) that terminates a Site-to-Site VPN connection.
  • Q: Does AWS have a VPN service? A: Yes, including Site-to-Site VPN and Client VPN, plus Transit Gateway VPN integration for scalable topologies.

AWS Client VPN: secure remote access

Beyond site-to-site connectivity, AWS offers Client VPN for remote workforce access to AWS and on‑premises resources.

  • Client VPN uses OpenVPN-based clients to connect users securely to your AWS resources.
  • It’s a user‑driven model: each client authenticates and tunnels securely into your VPC.
  • Useful for modern remote work scenarios where individual user access is required, rather than site‑to‑site connectivity.

Key considerations:

  • It’s ideal for employees or contractors who need encrypted access without impressively complex site‑to‑site configurations.
  • You’ll manage authentication (e.g., Active Directory, SSO) and authorization rules to control access.
  • Performance and scaling considerations depend on the number of clients and bandwidth requirements.

Feature table for deciding between site-to-site vs client VPN

DimensionSite-to-Site VPNClient VPNNotes
Primary audienceOn-prem networksRemote usersAudience alignment
Client software requiredNo for devicesYes for usersClient apps needed
Access modelNetwork-levelUser and device levelAccess control differences
Authentication optionsIAM roles / pre-shared keysAWS Managed Active Directory optionalAuth mechanisms
Certificate managementIPSec certificates sometimesTLS certificates for clientsCert lifecycle
Device compatibilityRouter/FirewallPersonal devicesCompatibility considerations
MonitoringCloudWatch metricsCloudWatch + VPN logsObservability
Offline accessYes with tunnelsNo without connectionAvailability nuance
Use whenBranch officesRemote workforceDecision hint
Pricing signalConnection countPer connection & dataCost driver

Compiled November 2026; check the provider's site for current details. Why will it not let me turn on totalav VPN thru app store

AWS Transit Gateway + VPN: scalable, centralized connectivity

If you’re dealing with multiple VPCs and multiple on‑premises networks, AWS Transit Gateway offers a hub-and-spoke model that simplifies connectivity.

  • Transit Gateway can attach VPCs and connect to VPNs (Site-to-Site) via VPN attachments.
  • It provides high availability, scalability, and centralized routing.
  • It’s particularly useful for complex environments with many VPCs and multiple on‑premises sites.

Comparison at a glance:

  • Site-to-Site VPN (using Virtual Private Gateway): Simple, good for a few connections, direct VPC attachment.
  • Transit Gateway with VPN: Scales well, centralizes routing, ideal for many VPCs/sites.
  • Client VPN: User-centric remote access, individual connections rather than site-level tunnels.

How the VPN connection actually works

Understanding the mechanics helps you plan deployment and troubleshooting.

  • Two VPN tunnels: AWS uses two IPSec VPN tunnels for reliability, terminating at a virtual private gateway on AWS and a customer gateway on your side.
  • BGP for dynamic routing: Many deployments use Border Gateway Protocol (BGP) to advertise routes between your network and AWS, enabling automatic route changes if a tunnel fails.
  • Encrypted traffic: All data traversing the VPN is encrypted to protect confidentiality and integrity across the public internet or private links.

If you’re using Transit Gateway:

  • You can connect your on‑premises networks to the Transit Gateway using Site-to-Site VPN attachments.
  • The Transit Gateway routes traffic between VPC attachments and VPN attachments, simplifying large networks.
AWS VPN gateway: Key points

Pros/Cons by VPN option (quick decision guide) I want to delete the Proton VPN from this PC

OptionProsConsBest-fit scenarioNot ideal when
Site-to-Site VPNSimple for fixed sites; managed by AWSLimited scalable per-hubSmall to medium networksLarge remote user base
Client VPNSecure remote access; flexible usersBinary client apps; potential bandwidth limitsRemote workforceVery large user populations
Transit Gateway + VPNScales great; centralized controlHigher complexity and costLarge, multi-VPC networksSmall, single-VPC setups

Compiled November 2026; check the provider's site for current details.

AWS VPN pricing: what to expect

Pricing for AWS VPN services is usage-based and depends on the VPN type and connections you establish.

  • Site-to-Site VPN pricing: billed per VPN connection-hour and data transfer. The connection is active for the duration you configure. You aren’t charged for idle time when the tunnel isn’t used, but a VPN connection-hour is billed once the tunnel is up.
  • Transit Gateway pricing: if you use Transit Gateway with VPN attachments, there’s an hourly charge for the Transit Gateway and data transfer associated with those attachments.
  • Client VPN pricing: billed per client connection-hour, plus data transfer.

A few practical tips:

  • Estimate your peak and off-peak data transfer to anticipate monthly costs.
  • If you have many VPCs and on‑premises sites, Transit Gateway can reduce management overhead, though it adds its own hourly costs.
  • Review data transfer direction: intra‑region vs inter‑region traffic has different cost implications.

Note: Always check the latest AWS pricing pages for Site-to-Site VPN, Transit Gateway, and Client VPN, as prices can change and region-specific differences exist.

Choosing the right AWS VPN gateway option

Ask these questions to guide your decision: V2rayn iOS: A Practical Guide to Using V2RayN on iPhone

  • How many on‑premises sites and VPCs need to connect? If you have several sites and VPCs, Transit Gateway with VPN attachments can simplify routing and scale more cleanly.
  • Do you need broad remote user access or only site-to-site connectivity? Client VPN is ideal for remote workers, while Site-to-Site VPN serves inter‑office connectivity.
  • What are your latency and throughput requirements? VPN tunnels can handle typical corporate workloads, but very high throughput or low-latency needs might push you toward optimized architectures or dedicated connections (like AWS Direct Connect in combination with VPN).
  • How dynamic are your routing needs? If you require automatic route updates and scalable routing, BGP with Transit Gateway can be beneficial.
  • What are your security and compliance requirements? Use strong authentication, least-privilege security groups and network ACLs, and consider integrating with your existing IAM/SSO strategies for Client VPN.

Table: quick comparison of VPN options (high level)

Option Use case Scaling Typical topology Key benefit Typical cost driver
Site-to-Site VPN (Virtual Private Gateway) Connect a single or few on‑prem sites to a VPC Moderate 1:1 or small hub-and-spoke with VPC Simple, reliable; good for small to medium deployments VPN connection-hours, data transfer
Transit Gateway + VPN Large networks with many VPCs and sites High Hub-and-spoke; multiple VPCs and sites Centralized routing, scalable Transit Gateway hours, VPN attachments, data transfer
AWS Client VPN Remote user access High if many clients; scalable with connections Remote users connect to VPCs securely User-based access with centralized management Client connection-hours, data transfer

Step-by-step high-level get-started checklist

StepActionOutcomeDependencies
1Define use caseClear targetStakeholders
2Choose optionDecision madeStep 1
3Create VPN gatewayResource createdIAM permissions
4Configure tunnels/clientsWorking tunnelsVPN device or client software
5Enable routingTraffic flowsRouting tables
6Test connectivityValidation resultsVPN up
7Monitor and optimizeOngoing postureCloudWatch setup

Compiled November 2026; check the provider's site for current details.

Best practices for deploying an AWS VPN gateway

  • Plan your addressing and routing first: Ensure there’s no overlap in IP ranges between your on‑premises network and the VPC.
  • Use dynamic routing when possible: BGP can simplify route management and failover.
  • Enable multiple tunnels for resilience: Confirm your VPN setup has two tunnels for redundancy.
  • Integrate with your security controls: Align security groups and network ACLs to permit only necessary traffic over the VPN.
  • Monitor and alert: Use CloudWatch to monitor VPN tunnels, data transfer, and error states, and set up alerts for tunnel down events.
  • Page through documentation for your devices: If you’re using a specific on‑premises gateway device, consult vendor guidance to ensure compatibility and optimal configuration with AWS.
  • Consider using Transit Gateway when appropriate: If you’re planning for growth, Transit Gateway reduces management overhead and centralizes routing.

How to get started (high level steps)

  • Decide on the VPN solution: Site-to-Site vs Client VPN vs Transit Gateway with VPN.
  • Prepare prerequisites: VPC with subnets, an appropriate CIDR plan, and an on‑premises gateway device or software.
  • Create a virtual private gateway and attach it to your VPC (for Site-to-Site).
  • Configure the customer gateway on your side and set up the VPN connection in AWS.
  • Update route tables in the VPC and ensure security groups allow VPN traffic.
  • Test failover and monitor performance: verify both tunnels work and traffic routes correctly.

If you’re starting to implement, you’ll likely begin with Site-to-Site VPN for a straightforward connection and consider transitioning to Transit Gateway later as your network grows or you require more centralized management.

Recommendation How to get a VPN for Edge on iPhone

If your goal is to securely connect a single or a few on‑premises networks to a VPC with room to grow, start with Site-to-Site VPN using a virtual private gateway. It offers a clear, straightforward setup and solid reliability with dual tunnels. If you anticipate multiple VPCs or many on‑premises sites, plan early for Transit Gateway to simplify routing and scaling. For remote workers needing secure access to resources, add AWS Client VPN in parallel or as a separate deployment, paired with your identity provider for seamless authentication. Finally, keep a close eye on pricing in your region and model your data transfer to keep your costs predictable while meeting security and performance goals.

VPN prices compared
VPNObfuscationFrom / monthPlanFree planRefundAlipayWeChatUnionPayCryptoWebsite opens in ChinaTrustpilot
ZoogVPNTurn on manually
Shadow
$2.49/mo27 months: $59.99Yes7 days✓✓✓✓✓ Yes (2.5 s)4.2/5 (195 reviews)
NordVPNTurn on manually
Obfuscated Servers / NordWhisper
$3.49/mo27 months: $94.23No30 days?✗✓✓✗ Blocked4.2/5 (51,628 reviews)
ExpressVPN✓ On by default
all servers
$3.00/mo28 months: $84No30 days✗✗✓✗✗ Blocked4.4/5 (29,706 reviews)
Surfshark✓ On by default
Camouflage, with OpenVPN
See siteSee siteNo30 days✗✗✗✓✗ Blocked4.3/5 (31,823 reviews)
Proton VPNTurn on manually
Stealth, free plan too
$2.99/mo12 months: $35.88Yes30 days✗✗✗✓✓ Yes (2.5 s)2.1/5 (1,040 reviews)
Astrill VPNTurn on manually
StealthVPN / OpenWeb
$12.50/mo24 months: $300NoSee site✗✗✗✓✗ Blocked1.3/5 (110 reviews)
Private Internet AccessTurn on manually
Shadowsocks, OpenVPN only
$2.03/mo40 months: $81.2No30 days✗✗✗✗✗ Blocked4.2/5 (11,033 reviews)
CyberGhostTurn on manually
selected servers
$2.19/mo28 months: $61.32No45 days✗✗✗✓✗ Blocked4.0/5 (24,178 reviews)
PureVPNTurn on manually
switch to OpenVPN
$1.69/mo60 months: $101.55No31 days?✗✗✓✓ Yes (2.6 s)4.4/5 (17,994 reviews)
AdGuard VPN✓ On by default
TrustTunnel
$2.99/mo24 months: $71.76Yes30 days✓✗✓✓Official site blocked; our special link opens (2.3 s)4.3/5 (290 reviews)
MullvadTurn on manually
QUIC / Shadowsocks / LWO
$5.61/mo€5/moNo14 days✗✗✗✓✗ Blocked3.2/5 (192 reviews)
WindscribeTurn on manually
Stealth / WStunnel
$5.75/mo12 months: $69YesSee site✗✗✗✓✗ Blocked4.7/5 (13,355 reviews)
StrongVPNTurn on manually
Scramble, OpenVPN TCP
See siteSee siteNo30 days✓✗✗✗✗ Blocked4.4/5 (2,695 reviews)
LightXtreme 闪连Not listed$7.08/mo12 months: $84.99Yes30 days✓✓✓✓✓ Yes (2.3 s)No page

Prices checked 2026-11-10 on each vendor's pricing page (cheapest long plan, USD). Check the vendor's checkout for the final price.

Obfuscation checked 2026-11-14 on each vendor's site and help center: "on by default" = nothing to set; "turn on manually" = switch protocol or mode in settings; "not listed" = the vendor describes no obfuscation.

Payment methods checked 2026-11-10 on each vendor's payment pages: all 14 take cards and PayPal; ✗ = not listed, ? = the vendor's own pages disagree.

China access: whether the official website opens from mainland China networks (tests the website only, not the VPN connection). Last checked 2026-11-11 04:07 Beijing time.

Trustpilot score and review count checked 2026-11-10.

© Healthlinemags 2026