Bitzu

SAA-C03 ยท Network security in the VPC

Site-to-Site VPN versus Direct Connect

Site-to-Site VPN versus Direct Connect (bandwidth, latency, encryption, setup time), VPN over Direct Connect, Client VPN and redundant connection designs.

Key points

  • Site-to-Site VPN: IPsec over the internet, customer gateway to virtual private gateway or transit gateway.
  • Quick, cheap, variable latency; 1.25 Gbps per tunnel; ECMP (dynamic routing, transit gateway) aggregates tunnels.
  • Direct Connect: private physical link; consistent latency, slower setup.
  • Not encrypted by default: add MACsec or VPN.
  • Client VPN: individual users.
  • Resilience: two Direct Connect locations or VPN backup.

Source: https://docs.aws.amazon.com/vpn/latest/s2svpn/vpn-limits.html

Practice questions

Single choice

Which option connects an on-premises data center to AWS over a private, dedicated network link instead of the public internet?

  1. AWS Site-to-Site VPN
  2. AWS Direct Connect
  3. AWS Client VPN
  4. VPC peering
Show answer

Answer: B. AWS Direct Connect

AWS Direct Connect provides a physical private connection through a Direct Connect location. Site-to-Site VPN and Client VPN both run over the internet, and VPC peering connects VPCs to each other, not to on-premises networks.

Select all that apply

Which statements describe AWS Site-to-Site VPN?

  1. Traffic is encrypted with IPsec and travels over the internet
  2. A standard VPN tunnel supports up to 1.25 Gbps
  3. It terminates on a virtual private gateway or a transit gateway
  4. It requires a physical cross-connect at a Direct Connect location
  5. It guarantees consistent, predictable latency
Show answer

Answer: A. Traffic is encrypted with IPsec and travels over the internet, B. A standard VPN tunnel supports up to 1.25 Gbps, C. It terminates on a virtual private gateway or a transit gateway

Site-to-Site VPN uses IPsec tunnels across the internet, a standard tunnel carries up to 1.25 Gbps, and the AWS side terminates on a virtual private gateway or a transit gateway. Physical cross-connects belong to Direct Connect, and because the path is the internet, latency is not guaranteed.

True or false

Because AWS Direct Connect is a private link, all traffic on it is encrypted by default.

Show answer

Answer: False

False. Private does not mean encrypted. Direct Connect traffic is not encrypted unless you add it, for example MACsec on supported dedicated connections or an IPsec VPN running over the Direct Connect link.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More SAA-C03 topics in this module