Cloud concept · Updated

Virtual Private Networks - Virtual private networks (VPNs) create logically private connections across an underlying network, commonly using encrypted tunnels to protect traffic.

In short

A VPN connects networks or individual users without requiring a dedicated physical circuit between every endpoint. In cloud architectures, VPNs provide hybrid connectivity and remote access, often with lower initial costs than dedicated connections but with performance and availability that depend on the underlying transport.

Cloud Concepts Hub →

6 key aspects of Virtual Private Networks

VPN design combines logical connectivity, traffic protection, routing, access control, and transport-aware cost and resilience planning.

01
Logical connectivity over shared transport

VPNs connect private networks or users across an underlying network without requiring a dedicated end-to-end physical circuit. The transport can be the internet or a private network.

02
Encryption and endpoint authentication

Cloud VPNs commonly use IPsec or TLS-based protocols to protect traffic in transit and authenticate tunnel endpoints. Confirm the actual security properties rather than assuming every technology labeled VPN provides encryption.

03
Site-to-site and remote-access patterns

Site-to-site VPNs connect whole networks through gateways, while remote-access VPNs connect individual devices. Select the pattern according to whether the requirement is hybrid network connectivity or user access.

04
Routing and access-control dependencies

Working tunnels still require forward and return routes, permitted traffic, and appropriate DNS resolution. Plan nonoverlapping address ranges and use static routing or dynamic routing according to scale and failover requirements.

05
Transport-dependent performance

Internet VPNs inherit internet congestion, latency variation, and outages. Encryption capacity and encapsulation overhead also affect usable throughput, so validate performance with representative workloads.

06
Cost and resilience trade-offs

Evaluate connection charges, data transfer, processing fees, gateway equipment, and operational effort against dedicated connectivity. Design redundant gateways and independent paths when availability requirements exceed what a single circuit can provide.

Cloud services for Virtual Private Networks

Amazon VPC supplies the private cloud networks, while AWS Site-to-Site VPN connects external networks through encrypted tunnels. A virtual private gateway can serve a single VPC, whereas AWS Transit Gateway centralizes routing for multiple VPCs and VPN connections. AWS Client VPN addresses individual remote users rather than branch-network connectivity. AWS Direct Connect offers a dedicated transport alternative and can coexist with VPN connectivity for encryption or backup requirements. Choose the combination by comparing traffic volume, latency tolerance, deployment time, redundancy needs, and total connection, transfer, and processing costs.

AWS Site-to-Site VPNAWS Site-to-Site VPN

Provides managed IPsec connectivity between a customer network and AWS through a virtual private gateway or transit gateway. Each connection includes two tunnels; configure both and consider customer-side redundancy rather than treating two tunnels as complete end-to-end resilience.

AWS Client VPNAWS Client VPN

Provides managed remote-access VPN connectivity for individual clients to authorized resources. Endpoint associations, routes, authorization rules, authentication, and security groups determine what connected users can reach.

AWS Transit GatewayAWS Transit Gateway

Acts as a regional routing hub that can connect multiple VPCs and site-to-site VPN attachments. It simplifies hub-and-spoke connectivity at scale, but attachment and data-processing charges must be included in the design.

AWS Direct ConnectAWS Direct Connect

Provides dedicated network connectivity to AWS rather than an internet VPN. It can complement a VPN through backup connectivity or supported private IP VPN configurations; Direct Connect does not encrypt traffic by default.

Amazon VPCAmazon VPC

Provides the cloud network containing the subnets and resources reached through a VPN. Route tables, security groups, and network ACLs control connectivity inside the VPC; a VPC alone does not establish a VPN to an external network.

Virtual Private Networks exam questions

Real practice exam questions on Virtual Private Networks, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAA-C03

A company already provides employees with encrypted remote access to its corporate network through an on-premises remote-access gateway. The corporate network connects to a single VPC through an existing BGP-based AWS Site-to-Site VPN connection. Both connections have sufficient unused capacity.

Ten administrators now need to access private IP addresses of EC2 instances in the VPC from their laptops. Their remote-access address pool does not overlap with the corporate network or VPC CIDR blocks. Currently, the remote-access gateway does not forward traffic to the VPC, and the corporate router does not advertise the remote-access address pool to AWS. Company policy permits forwarding this traffic through the corporate network, and the resulting latency is acceptable.

Which solution provides encrypted connectivity with the LOWEST additional fixed AWS connectivity charges?

Show answerCORRECT ANSWER

Configure the remote-access gateway to forward VPC-bound traffic to the corporate router. Advertise the remote-access address pool over the existing BGP sessions, ensure VPC return routes use the existing VPN, and permit the traffic in the relevant security controls.

The administrators can use the existing encrypted remote-access connection to reach the corporate network and the existing encrypted Site-to-Site VPN to reach AWS. Forwarding, destination routes, return routes, and security permissions complete the path. Because both connections have spare capacity, this solution requires no additional fixed AWS connectivity charges.

ANS-C01

A company connects application VPCs in several AWS accounts to a central transit gateway. Two dynamically routed AWS Site-to-Site VPN connections connect the transit gateway to two on-premises routers. All four IPsec tunnels and BGP sessions are established. Each tunnel has sufficient capacity for an individual application flow, but the aggregate AWS-to-on-premises traffic exceeds the capacity of any two tunnels.

Both routers advertise the same on-premises prefixes. One router prepends its customer ASN twice to every advertisement toward AWS; all other relevant BGP attributes are equal. VPN ECMP support is disabled on the transit gateway. There are no static routes for the on-premises prefixes. The routers support concurrent forwarding across all four tunnels, and the on-premises network permits asymmetric paths. VPC routing, transit gateway route propagation, and security controls are correct.

The company must distribute many independent AWS-to-on-premises flows across all four existing tunnels without adding connections or changing application addressing.

Which configuration meets these requirements?

Show answerCORRECT ANSWER

Enable VPN ECMP support on the transit gateway and remove the customer ASN prepending so that all four tunnels advertise equal-length AS paths for the same prefixes.

Transit Gateway supports ECMP across dynamically routed Site-to-Site VPN tunnels. Enabling VPN ECMP and providing otherwise equivalent routes with equal-length AS paths makes all four tunnels eligible for multipath forwarding. Multiple independent flows can then use the aggregate tunnel capacity; an individual flow remains assigned to a path.

Practice Virtual Private Networks in a full exam

Questions on Virtual Private Networks in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Virtual Private Networks

3 min read

A virtual private network creates a logical connection across another network so that geographically separated systems can communicate as part of a controlled private environment. Cloud VPN connections commonly encrypt and authenticate traffic using IPsec or TLS-based protocols. The tunnel endpoints encapsulate application packets, transport them across the underlying network, and recover the original packets at the destination. Although cloud VPNs commonly use the public internet, a VPN can also run over private transport.

Two common applications are site-to-site connectivity and remote access. A site-to-site VPN connects an office or data center network to a cloud network through gateways. For example, a company can connect its warehouse network to private application servers in the cloud without giving those servers public IP addresses. A remote-access VPN connects individual devices, such as engineers' laptops, to authorized private resources. These patterns solve different access requirements and have different authentication, capacity, and pricing considerations.

Successful connectivity requires more than an established tunnel. Both sides need routes for the destination networks and a valid return path. Firewalls, cloud security controls, and VPN authorization rules must permit the intended traffic. Address ranges should generally not overlap; overlapping networks may require translation or an addressing redesign. Private DNS resolution also needs explicit planning when clients must reach applications by internal names. Dynamic routing with BGP can exchange routes and support failover, while static routes may be sufficient for a small, stable topology.

For cost optimization, compare total operating costs rather than assuming that a VPN is always cheapest. Internet-based VPNs typically avoid dedicated-circuit provisioning and can suit modest traffic volumes, temporary projects, branch offices, or backup connectivity. Costs can include VPN connection hours, remote-client connection hours, data transfer, transit-hub processing, internet access, and customer gateway equipment. A dedicated connection can become attractive for sustained traffic or predictable network performance, but its economics also depend on carrier charges, port capacity, location, and redundancy requirements.

A VPN does not reserve internet bandwidth or eliminate congestion. Throughput depends on gateway capacity, encryption processing, tunnel limits, packet size, and the available network path. Encapsulation adds overhead and can cause fragmentation or connectivity problems unless MTU and TCP MSS settings are appropriate. A large migration may therefore take longer over a VPN than the nominal internet circuit speed suggests. Measure application throughput and latency rather than relying only on link specifications.

High availability requires redundant paths and tested routing behavior. Multiple tunnels protect against some endpoint failures, but tunnels sharing one customer router or internet circuit still have a common failure point. Critical workloads may require redundant customer gateways and separate internet providers. A VPN can also back up a dedicated connection, provided that routing preferences are deliberate and the backup path has enough capacity for essential traffic.

Private connectivity and encryption are separate properties. A dedicated private circuit is not automatically encrypted, and some provider-managed VPN technologies provide traffic isolation without cryptographic protection. Likewise, encryption does not authorize every connected user to access every resource. Apply least-privilege access, strong authentication, logging, and key or certificate rotation. For architecture questions, choose an internet VPN when rapid deployment and low initial cost fit the workload; evaluate dedicated connectivity when sustained capacity or more consistent network performance justifies the additional expense.

Learn Virtual Private Networks in lessons

3 short lessons on Virtual Private Networks in 2 certification courses.

Open the lessons