Remote user connectivity
AWS Client VPNA VPN provides an encrypted connection over a network to reach private resources. gives individual users encrypted access from their devices to AWS and connected on-premises resources. It uses an OpenVPN-based client and Transport Layer SecurityTLS encrypts the connection between a remote VPN client and its endpoint. (TLS), the protocol that encrypts the connection. Site-to-Site VPN connects networks through IPsecIPsec is the network encryption protocol suite used by Site-to-Site VPN., a suite of network encryption protocols.
How it works
- Create an endpointA Client VPN endpoint terminates and manages remote client sessions., the connection point for user sessions, with a server certificate in ACM in the endpoint Region. Choose user authentication through Active Directory or SAMLSAML enables federated user authentication through an identity provider., an identity federation standard, or mutual certificate authentication that checks the client’s certificate. A combined configuration requires both checks to succeed.
- For an IPv4 setup, choose a non-overlapping client CIDRCIDR notation describes an IP address range using an address and a prefix length., the address range assigned to connected clients. It must be from
/22through/12and cannot change after creation. - Choose a network association. A subnet-based endpoint connects through VPC subnets. A Transit Gateway-associated endpoint connects directly to the network hub; one endpoint cannot mix the two association types.
- Add destination routes and authorization grants. Authentication identifies who connected; authorization decides which destination networks that user may access. Rules grant access, use the most specific matching network prefix, and process
0.0.0.0/0, any IPv4 destination, last. - For subnet-based access, allow traffic at the destination resource’s security groupA security group controls which network traffic can reach a resource., a virtual firewall, from the Client VPN association security group. Keep the same destination routes on all subnet associations.
- Choose traffic routing. Full tunnel is the default. Split tunnelSplit tunnel sends traffic matching configured VPN destination routes through the tunnel while other traffic uses local routing. sends only traffic matching endpoint routes through the VPN. Connection logs in CloudWatch Logs help diagnose access failures.
| Authentication choice | What is checked |
|---|---|
| Active Directory | User identity through a directory |
| SAML federation | User identity through an external identity provider |
| Mutual authenticationMutual authentication uses client certificates to authenticate VPN clients. | Client certificate |
For subnet-based endpoints, use subnets in the same VPC and different Availability Zones, separate locations that provide failure isolation. AWS recommends at least two for redundancy. Each subnet must be /27 or larger and retain at least 20 free addresses.
Direct Transit Gateway attachment preserves client source IPs. Source network address translationSNAT replaces the source IP address of outgoing traffic with another address. (SNAT) means replacing a packet’s source address; this attachment does not apply it. Destination VPCs therefore need return routes to the client CIDR through the Transit Gateway.
Exam cues
- If the question says individual remote users on laptops, think Client VPN, because it creates client sessions rather than a network-to-network IPsec connection.
- If the question says users connect but resources remain unreachable, think authorization, routes and security groups, because successful login alone does not open the network path.
- If the question says keep ordinary internet traffic off the VPN, think split tunnel with private destination routes, because only matching routes use the tunnel.
- If the question says direct remote access to networks on a Transit Gateway, think Transit Gateway-associated Client VPN, because it can attach directly without an intermediate VPC.
Remember
-
Internet access through a public target subnet needs an endpoint default route and authorization, plus a subnet route to an internet gateway and outbound security-group access.
-
Endpoint associations and client connections are billed hourly; data transfer and optional logging can add charges.
-
Default transport and port: UDP and 443. TCP and port 1194 are also supported.
-
Split tunnel is disabled by default. Updating its endpoint routes resets all client connections.
-
Client IPv4 CIDR:
/22through/12, fixed after creation and non-overlapping. -
Target subnet:
/27or larger with at least 20 available addresses. -
Standard authorization requires explicit grants. Quickstart automatically creates a VPC grant, routes and associations.
Trap: SAML or directory login still needs a server certificate. Network authorization and routing are separate from authentication.
TLS authentication
Authorized routed access
From the AWS docs (25)
- Client VPN provides encrypted TLS remote access for individual users through an OpenVPN-based client to AWS and connected on-premises resources.
- Site-to-Site VPN connects an on-premises network to AWS using IPsec rather than individual remote user sessions.
- Client VPN supports Active Directory, mutual certificate authentication or SAML federated authentication; mutual authentication can be combined with either user-based method.
- When mutual and user-based authentication are combined, both methods must succeed.
- Every Client VPN authentication method requires a server certificate in ACM in the endpoint Region.
- Client VPN authorization rules grant network access to selected users or groups; without a matching grant, access is denied.
- Client VPN authorization rules use longest prefix matching, with the IPv4 any-destination rule 0.0.0.0/0 processed last; rules grant access and cannot explicitly deny it.
- For subnet-based endpoints, associate at least one target subnet; further subnets must be in the same VPC and different Availability Zones.
- AWS recommends associating at least two target subnets in different Availability Zones for subnet-based endpoint redundancy.
- A Client VPN target subnet must be /27 or larger and retain at least 20 available IP addresses.
- The client IPv4 CIDR must be from /22 through /12, cannot overlap target networks, the VPC or endpoint routes, and cannot be changed after endpoint creation.
- Subnet association adds the local VPC route; additional destination networks need endpoint routes and authorization rules.
- Each associated subnet should have an identical set of Client VPN routes to avoid intermittent destination access.
- For subnet-based VPC access, allow traffic in resource security groups from the security group applied to the Client VPN subnet association.
- By default, split tunnel is disabled and client traffic is routed through the VPN tunnel.
- Split tunnel installs endpoint route table routes on clients and sends only traffic matching those routes through the VPN.
- Changing a split-tunnel endpoint route table resets all client connections; adding 0.0.0.0/0 is not recommended because it can disrupt connectivity.
- Client VPN connection logging can send connection events to CloudWatch Logs for troubleshooting.
- Client VPN supports TCP or UDP on ports 443 or 1194; the default transport is UDP and the default port is 443.
- Creating a Client VPN endpoint defaults its transport protocol to UDP.
- Client VPN can attach directly to a Transit Gateway for access to connected networks; subnet associations and Transit Gateway associations cannot be mixed in one endpoint.
- Transit Gateway-associated Client VPN endpoints preserve client source IPs without source network address translation; destination VPCs need return routes for the client CIDR.
- Client VPN Quickstart creates a VPC authorization grant, target subnet associations and VPC routes automatically.
- AWS Client VPN bills each endpoint association and each client VPN connection by the hour; internet data transfer and optional logging add separate charges.
- In the public-subnet Client VPN internet-access setup, clients need an endpoint route and authorization for 0.0.0.0/0, a subnet route to an attached internet gateway, and outbound security-group access.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 12 cards as a list
Remote employees need encrypted access from their laptops to private AWS resources. Which AWS VPN service fits?
Client VPN. Users connect with an OpenVPN-based client. Site-to-Site VPN connects an on-premises network to AWS.
A Client VPN user authenticates successfully but cannot access a VPC resource through a subnet-based endpoint. What controls should the team check?
Destination authorization, endpoint and network routes, and resource security group access from the Client VPN association security group. Authentication alone does not grant network access.
Does SAML authentication remove the requirement for an ACM server certificate on an AWS Client VPN endpoint?
No. Every authentication method requires a server certificate in ACM in the endpoint Region.
An AWS Client VPN endpoint combines mutual certificate authentication with Active Directory. Can a valid client certificate alone authenticate the user?
No. Both the certificate-based and user-based methods must succeed.
Remote users should send only private destination traffic through AWS Client VPN. Which mode fits?
Split tunnel. It installs endpoint routes on the client and sends matching traffic through the tunnel. Route table changes reset connected clients.
Remote users need access to an additional network through AWS Client VPN. What network controls must be configured?
Add an endpoint route and an authorization rule for the destination network.
What IPv4 client CIDR constraints apply when creating an AWS Client VPN endpoint?
Choose /22 through /12 without overlapping the VPC, target networks or endpoint routes. The client IPv4 range cannot be changed after creation.
Can one AWS Client VPN endpoint use both VPC subnet associations and a direct Transit Gateway association?
No. Choose one association type. A Transit Gateway-associated endpoint preserves client source IPs and requires return routes to the client CIDR.
What default tunnel transport, port and routing mode does an AWS Client VPN endpoint use?
UDP, port 443 and full-tunnel routing. TCP and port 1194 are supported alternatives, and split tunnel can be enabled.
A subnet-based AWS Client VPN endpoint has intermittent access to an added destination network. What route configuration should the team inspect?
Ensure every associated subnet has the same endpoint destination route set, and confirm authorization for that network.
For AWS Client VPN remote access, which resources incur hourly charges even before considering data transfer?
Each endpoint association and each client VPN connection. Budget separately for internet data transfer and enabled logging.
AWS Client VPN users can reach their VPC but need internet access through an associated public subnet. What network configuration is required?
An endpoint route and authorization rule for
0.0.0.0/0, a subnet route to an attached internet gateway, and security-group rules allowing outbound traffic.