Arkinu
AWS service comparison

AWS Client VPN vs AWS Site-to-Site VPN: differences and when to use each

AWS Client VPN
AWS Site-to-Site VPN

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Networking and Content Delivery

AWS Client VPN

Managed client-based VPN that lets each user securely access your AWS resources and your on-premises network from any location, using an OpenVPN-based VPN client. It removes the need to deploy and maintain your own remote access VPN solution.

Exam phrases that point here

  • «give employees working from home secure remote access to private resources in the VPC»

    Client VPN is a managed remote-access VPN: each person connects from their own device with an OpenVPN-based client and reaches private resources as if they were on the network.

    When not: If what needs to be connected is an entire office or data center network, rather than individual people, the clue points to AWS Site-to-Site VPN.

  • «avoid deploying and maintaining your own VPN servers for remote access»

    With Client VPN there are no VPN servers to install or manage: AWS runs the endpoint and the administrator only configures authentication, routes, and access rules.

    When not: If the scenario only asks to connect two networks permanently, the managed service that fits is Site-to-Site VPN, not Client VPN.

  • «authenticate VPN users with Active Directory or a SAML identity provider»

    Client VPN supports authentication with Active Directory (through AWS Directory Service), federated authentication with SAML 2.0, and mutual authentication with certificates, and it allows authorization rules per group.

    When not: If only mutual certificate authentication is used, there are no user groups: to give each group different access you would have to create several endpoints.

  • «only the traffic destined for AWS should go through the VPN»

    With split-tunnel, the device sends through the tunnel only the traffic to the networks in the endpoint's route table; everything else goes out through the user's local connection, which also reduces data transfer out of AWS.

    When not: If the company needs all of the user's traffic, including internet traffic, to go through AWS (for example, to control it), the default behavior is kept, which sends everything through the tunnel.

  • «remote users must also be able to reach the on-premises network»

    The Client VPN endpoint can have routes to networks connected to the VPC, such as a data center joined through Site-to-Site VPN or Direct Connect, along with its authorization rule.

    When not: Client VPN only covers the stretch from the user to AWS. If the VPC is not yet connected to on-premises, you also need a Site-to-Site VPN or Direct Connect.

Study AWS Client VPN →

Networking and Content Delivery

AWS Site-to-Site VPN

Encrypted IPsec VPN connection between your on-premises network and your VPCs, terminated on AWS at a virtual private gateway, a transit gateway, or AWS Cloud WAN. It lets VPC resources and devices on your local network communicate; each connection includes two tunnels for high availability.

Exam phrases that point here

  • «quickly connect the on-premises network to the VPC over the internet with encryption»

    Site-to-Site VPN creates encrypted IPsec tunnels over the internet connection you already have. No physical circuit needs to be provisioned.

    When not: If the scenario requires high bandwidth and consistent performance, or that traffic not traverse the internet, the answer leans toward AWS Direct Connect.

  • «connect an entire office or data center network to AWS»

    Site-to-Site VPN links entire networks: the site's router (customer gateway) maintains the tunnel and all the devices on that network reach the VPC.

    When not: If the ones connecting are individual people from their laptops, at home or traveling, the clue points to AWS Client VPN, not to a site-to-site VPN.

  • «low-cost backup connection for Direct Connect»

    A VPN to the same virtual private gateway kicks in if Direct Connect goes down, without paying for a second dedicated circuit.

    When not: The backup VPN does not offer the same performance. If the backup must match the primary link, AWS recommends a second Direct Connect connection; and for Local Zones, a VPN backup is not supported.

  • «encrypt the traffic that travels over Direct Connect»

    A private IP VPN runs over a Direct Connect transit VIF and terminates on a transit gateway, so traffic is encrypted with IPsec without going out to the internet.

    When not: On supported dedicated connections, MACsec encrypts the link at its own layer and may be the expected answer. And a private IP VPN requires a transit gateway: it cannot be done with a virtual private gateway.

  • «improve VPN performance from sites far from the Region»

    Accelerated Site-to-Site VPN makes traffic enter the AWS global network as soon as possible, with more consistent behavior than the public internet.

    When not: It only exists with a transit gateway, not with a virtual private gateway. And if the problem is link capacity rather than the path over the internet, think of Direct Connect.

  • «exceed the bandwidth of a single VPN tunnel»

    With a transit gateway (or with AWS Cloud WAN) you can use large bandwidth tunnels, up to 5 Gbps instead of 1.25 Gbps. And with a transit gateway you can enable ECMP: traffic is spread across several VPN tunnels and connections, adding up their capacity.

    When not: With a virtual private gateway all VPNs share a single aggregate limit, so adding connections does not add bandwidth. For high, stable capacity, Direct Connect.

Often paired with

  • AWS Transit Gateway
Study AWS Site-to-Site VPN →