Site-to-Site VPN uses two tunnels per connection and supports standard or large tunnel bandwidth.
Site-to-Site VPN basics
AWS Site-to-Site VPN links a whole remote network to a VPCA logically isolated virtual network in AWS. with an encrypted connection.
How it works
- Configure a customer gatewayAn AWS resource containing information about the device on your side of a VPN connection. for the remote network.
- Create the VPN connection to AWS.
- Traffic between the networks flows through the tunnelsAn encrypted link that carries traffic between a customer network and AWS..
Exam cues
- If the question says connect an on-premises network to a VPC quickly, think Site-to-Site VPN.
Remember
- Connects networks, not individual users.
Trap: Site-to-Site VPN connects networks; Client VPN connects individual users.
Tunnels, connectivity, and bandwidth
AWS Site-to-Site VPN connects an on-premises network to a virtual private cloudA logically isolated virtual network in AWS. (VPC), an isolated virtual network in AWS, using IPsecA protocol suite used by Site-to-Site VPN to secure network traffic., a protocol for securing IP traffic. Each connection has two encrypted tunnelsAn encrypted link that carries traffic between a customer network and AWS. for availability.
How it works
- Select an AWS endpoint: a virtual private gatewayThe AWS-side VPN endpoint that can attach to one VPC. for one VPC, or a transit gateway for multiple VPCs and on-premises networks.
- Configure the customer gateway devicePhysical equipment or software on the customer side of a VPN connection.. The connection has two tunnels that terminate in different Availability Zones.
- Configure VPC route tables to send traffic for the remote network to the AWS gateway.
Exam cues
- If the question says encrypt Direct Connect traffic without public addresses, think private IP Site-to-Site VPN, because it encrypts traffic over Direct Connect.
- If the question says a VPN is up but VPC instances cannot reach the remote network, think subnet route tables, because route propagation can add VPN routes for a virtual private gateway.
- If the question asks for tunnel bandwidth, think standard or Large Bandwidth Tunnels, because their per-tunnel limits differ.
Remember
- Standard tunnels support up to 1.25 Gbps each by default; Large Bandwidth Tunnels support up to 5 Gbps each.
- Both tunnels must use the same bandwidth setting. Large Bandwidth Tunnels require Transit Gateway or Cloud WAN and a fixed customer gatewayAn AWS resource containing information about the device on your side of a VPN connection. IP address.
- Large Bandwidth Tunnels do not support accelerated VPN.
- Direct Connect does not encrypt traffic by default.
- Pricing: per connection-hour (partial hours round up) plus data transfer.
Trap: A virtual private gateway cannot use Large Bandwidth Tunnels. Use Transit Gateway or Cloud WAN for that option.
Configure the first encrypted tunnel.
The first tunnel reaches the AWS gateway.
Configure the second encrypted tunnel for redundancy.
The second tunnel reaches the AWS gateway in another Availability Zone.
From the AWS docs (15)
- Site-to-Site VPN connects an on-premises network to VPCs using IPsec.
- A VPC is a logically isolated virtual network in AWS.
- A virtual private gateway attaches to one VPC; a transit gateway connects multiple VPCs and on-premises networks.
- Each VPN connection has two encrypted tunnels, which can both be used for high availability.
- Each tunnel terminates in a different Availability Zone.
- Configure the customer gateway device and VPC route tables to direct traffic for the remote network to the AWS gateway.
- Standard tunnel bandwidth is up to 1.25 Gbps per tunnel by default; Large Bandwidth Tunnels support up to 5 Gbps per tunnel.
- Large Bandwidth Tunnels require a transit gateway or Cloud WAN, both tunnels must use the same bandwidth, and accelerated VPN is not supported.
- Large Bandwidth Tunnels require a customer gateway with a fixed IP address.
- Private IP Site-to-Site VPN can encrypt Direct Connect traffic without public IP addresses.
- Direct Connect does not encrypt traffic in transit by default.
- With a virtual private gateway, enable route propagation on the subnet route tables so the VPN static prefixes or BGP routes appear there when the connection is up.
- If the customer gateway device sits behind NAT, register the NAT device public IP address as the customer gateway address and allow UDP 500 and 4500 for NAT traversal.
- Site-to-Site VPN tunnel endpoints authenticate with a pre-shared key, the default, or with certificates.
- AWS Site-to-Site VPN charges for each connection-hour the connection is provisioned, with partial hours billed as full hours, plus standard data transfer charges.
VPN CloudHub
AWS VPN CloudHub turns the virtual private gatewayThe AWS-side VPN endpoint that can attach to one VPC. into a hub, so branch offices that already have VPNs to AWS can reach each other through it.
How it works
- Create one virtual private gateway.
- Create a customer gatewayAn AWS resource containing information about the device on your side of a VPN connection. per site, each with a unique BGPA protocol that exchanges routing information between networks. ASN.
- Create a dynamically routed VPN connection from each site to that gateway.
- Each site advertises its prefix; the gateway re-advertises it to the other sites.
Exam cues
- If the question says branch offices must communicate with each other over their existing AWS VPNs, think VPN CloudHub.
- If the question says many VPCs plus many sites at scale, think Transit Gateway.
Remember
- One virtual private gateway, BGP, unique ASN per site.
- No overlapping site IP ranges.
Trap: Static VPN routes don’t work for CloudHub. Each site needs a dynamically routed (BGP) connection so prefixes can be re-advertised.
From the AWS docs (3)
- AWS VPN CloudHub lets sites with Site-to-Site VPN connections to the same virtual private gateway communicate with each other, in a hub-and-spoke model, with or without a VPC.
- For VPN CloudHub you create one virtual private gateway, a customer gateway per site with a unique BGP ASN, and a dynamically routed VPN connection from each site.
- Sites connected through VPN CloudHub must not have overlapping IP ranges, and each advertises its own prefix over BGP.
VPN redundancy and routing design
AWS Site-to-Site VPN design choices affect tunnelAn encrypted link that carries traffic between a customer network and AWS. redundancy, routing and bandwidth. A customer gatewayAn AWS resource containing information about the device on your side of a VPN connection. is the AWS resource that describes the physical or software customer gateway devicePhysical equipment or software on the customer side of a VPN connection..
How it works
- Configure both tunnels so traffic can use the available tunnel if one becomes unavailable.
- For protection against a customer device failure, add a second VPN connection with a second customer gateway device. This also lets you maintain one device while using the other.
- Choose static routing or dynamic routing with Border Gateway ProtocolA protocol that exchanges routing information between networks. (BGP), which exchanges routes. Cloud WAN VPN connections require BGP.
- To increase aggregate bandwidth beyond one tunnel, use Equal Cost Multi PathRouting that can use multiple paths to increase available VPN bandwidth. (ECMP) routing across multiple VPN connections. Transit Gateway can use ECMP on VPN attachments to spread traffic across tunnels. VPN scaling and Transit Gateway ECMP
Exam cues
- If the question says an AWS tunnel may fail, think configure both tunnels, because traffic can use the available tunnel.
- If the question says the customer router may fail, think a second VPN connection and customer gateway device, because two tunnels alone do not protect against that device failing.
- If the question says a Direct Connect circuit needs backup, think a Large Bandwidth Tunnel, because it can provide backup or overlay connectivity.
- If the question says aggregate bandwidth must exceed one tunnel, think ECMP across multiple VPN connections, because it can spread traffic across tunnels.
Remember
- Outside tunnel addresses can be public IPv4, private IPv4 or IPv6. Public IPv4 is the default.
- A single connection cannot carry IPv4 and IPv6 traffic simultaneously. A virtual private gatewayThe AWS-side VPN endpoint that can attach to one VPC. VPN does not support IPv6 traffic.
- Large Bandwidth Tunnels require Transit Gateway or Cloud WAN. Both tunnels must use the same bandwidth, and accelerated VPN is not supported.
Trap: Two tunnels on one customer gateway device do not protect against that device failing. Add a second VPN connection with a second device.
From the AWS docs (9)
- Configure both tunnels for redundancy; when one becomes unavailable traffic automatically uses the available tunnel.
- Large Bandwidth Tunnels require a transit gateway or Cloud WAN, both tunnels must use the same bandwidth, and accelerated VPN is not supported.
- Large Bandwidth Tunnels can provide backup or overlay connectivity for Direct Connect circuits.
- Equal Cost Multi Path routing across multiple VPN connections can increase aggregate bandwidth beyond that of a single tunnel.
- Outside tunnel address options include public IPv4, private IPv4 and IPv6; public IPv4 is the default.
- Site-to-Site VPN supports static routing or dynamic routing using BGP; Cloud WAN VPN connections support BGP but not static routing.
- VPN connections on a virtual private gateway do not support IPv6 traffic, and a single connection cannot carry both IPv4 and IPv6 traffic simultaneously.
- AWS Transit Gateway supports ECMP routing, which can be turned on for VPN attachments to spread traffic across several VPN tunnels.
- A second Site-to-Site VPN connection with a second customer gateway device protects against losing connectivity when one customer device fails and allows maintenance on a device.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 19 cards as a list
A company wants a quick, encrypted connection between its office network and a VPC over the internet. Which service fits?
AWS Site-to-Site VPN.
What is the difference between a Site-to-Site VPN customer gateway and customer gateway device?
The customer gateway is an AWS resource describing the device. The device is physical or software equipment on the customer side.
What are the tunnel and bandwidth options for AWS Site-to-Site VPN?
Each connection has two encrypted tunnels. Standard bandwidth is up to 1.25 Gbps per tunnel by default; Large Bandwidth Tunnels support up to 5 Gbps per tunnel on Transit Gateway or Cloud WAN.
A company needs encrypted Direct Connect traffic without public IP addresses. Which VPN option fits?
Private IP Site-to-Site VPN over Direct Connect.
A team assumes Direct Connect encrypts traffic by default. What should it know before using Site-to-Site VPN?
Direct Connect does not encrypt traffic by default. Private IP Site-to-Site VPN can encrypt it without public IP addresses.
A Site-to-Site VPN is up, but instances cannot reach on-premises hosts. The VPC uses a virtual private gateway. What is often missing?
Route propagation (or static routes) in the subnet route tables toward the virtual private gateway.
What does an AWS Site-to-Site VPN connection cost while it is provisioned but idle?
The hourly connection charge still applies; data transfer charges add only for traffic sent.
A company has six branch offices, each with a Site-to-Site VPN to AWS, and needs the branches to talk to each other cheaply over the existing VPNs. Which feature fits?
AWS VPN CloudHub: all VPNs to one virtual private gateway, BGP re-advertises each site's prefix to the others.
What does each customer gateway need for AWS VPN CloudHub to work?
A unique BGP ASN and a dynamically routed VPN connection to the shared virtual private gateway.
Two branch offices use the same 10.0.0.0/24 range. Can AWS VPN CloudHub connect them?
No. CloudHub sites must not have overlapping IP ranges.
A company needs its Site-to-Site VPN to survive an AWS tunnel outage. What should it configure?
Configure both tunnels. If one becomes unavailable, traffic uses the available tunnel.
Can a Site-to-Site VPN attached to a virtual private gateway use Large Bandwidth Tunnels?
No. Large Bandwidth Tunnels require Transit Gateway or Cloud WAN.
What can provide backup connectivity for a Direct Connect circuit?
A Site-to-Site VPN Large Bandwidth Tunnel can provide backup connectivity.
How can a Site-to-Site VPN design scale aggregate bandwidth beyond one large tunnel?
Use Equal Cost Multi Path routing across multiple VPN connections.
What outside tunnel address types can an AWS Site-to-Site VPN use, and what is the default?
Public IPv4, private IPv4 or IPv6. Public IPv4 is the default.
A Cloud WAN Site-to-Site VPN needs to exchange routes dynamically. Which routing protocol is required?
Use BGP. Cloud WAN VPN connections do not support static routing.
Can one Site-to-Site VPN connection carry both IPv4 and IPv6 traffic simultaneously?
No. Separate VPN connections are needed; a virtual private gateway VPN does not support IPv6 traffic.
Traffic over Site-to-Site VPN has outgrown one connection. Which design raises aggregate VPN throughput?
Terminate the VPN connections on a transit gateway with ECMP turned on and add more VPN tunnels. Transfer Acceleration and Global Accelerator do not apply to VPN links.
A Site-to-Site VPN already has two tunnels, but both end on a single on-premises router. How can the design survive that router failing?
Add a second VPN connection to a second customer gateway device. The two tunnels protect the AWS side; the customer device stays a single point of failure.