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.