Arkinu
AWS service comparison

AWS Direct Connect vs AWS Site-to-Site VPN: differences and when to use each

AWS Direct Connect
AWS Site-to-Site VPN

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Networking and Content Delivery

AWS Direct Connect

Dedicated network connection between your internal network and an AWS Direct Connect location over a standard Ethernet fiber-optic cable. It gives you access to your VPCs and to public AWS services while bypassing internet service providers in the network path.

Exam phrases that point here

  • «dedicated, private network connection between the data center and AWS»

    Direct Connect links your network to AWS over a dedicated physical connection that does not traverse the internet. It is the typical answer when the scenario rules out the internet as the path.

    When not: If the requirement is an encrypted connection that must be ready soon or that needs little bandwidth, AWS Site-to-Site VPN fits better: Direct Connect requires provisioning a physical circuit, your own or through a partner, and that is not immediate.

  • «consistent network performance and predictable latency to AWS»

    Because it does not depend on the variable path of the internet, a dedicated connection offers more stable behavior than a VPN over the internet.

    When not: If the ones suffering the latency are users spread across the internet rather than your own data center, the clue points to Amazon CloudFront or AWS Global Accelerator, not to Direct Connect.

  • «continuously transfer large volumes of data from on-premises facilities»

    A high-capacity dedicated connection is suited to moving data steadily between the data center and AWS, with no data limit beyond the port's capacity.

    When not: If it is a one-time migration of many terabytes and the available link is slow, a physical transfer is preferable. AWS Snow Family is no longer offered to new customers: AWS suggests AWS Data Transfer Terminal or partner solutions. And if connectivity already exists and the task is to copy files, AWS DataSync may be the missing piece.

  • «encrypt the traffic that travels over Direct Connect»

    A private connection does not mean it is encrypted. You can add MACsec on supported dedicated connections or set up an IPsec VPN over Direct Connect.

    When not: If the scenario does not require a dedicated connection and only asks for encrypted connectivity, an AWS Site-to-Site VPN over the internet solves the encryption by itself.

  • «access VPCs in multiple Regions with a single connection»

    A Direct Connect gateway is a global resource: with a connection at one location you can reach VPCs in any Region (except China).

    When not: The Direct Connect gateway does not let those VPCs talk to each other. If you also need to connect VPCs to one another, think of AWS Transit Gateway or VPC peering.

  • «high availability for the hybrid connection with Direct Connect»

    The recommendation is to have more than one connection, ideally at different locations, so that a failure or maintenance does not cut off access.

    When not: A LAG is not enough: it only protects if a link fails, not if the AWS device where it terminates fails. And if the budget does not cover a second connection, a backup Site-to-Site VPN is the inexpensive option, with lower performance.

Often paired with

  • AWS Transit Gateway
Study AWS Direct Connect →

Networking and Content Delivery

AWS Site-to-Site VPN

Encrypted IPsec VPN connection between your on-premises network and your VPCs, terminated on AWS at a virtual private gateway, a transit gateway, or AWS Cloud WAN. It lets VPC resources and devices on your local network communicate; each connection includes two tunnels for high availability.

Exam phrases that point here

  • «quickly connect the on-premises network to the VPC over the internet with encryption»

    Site-to-Site VPN creates encrypted IPsec tunnels over the internet connection you already have. No physical circuit needs to be provisioned.

    When not: If the scenario requires high bandwidth and consistent performance, or that traffic not traverse the internet, the answer leans toward AWS Direct Connect.

  • «connect an entire office or data center network to AWS»

    Site-to-Site VPN links entire networks: the site's router (customer gateway) maintains the tunnel and all the devices on that network reach the VPC.

    When not: If the ones connecting are individual people from their laptops, at home or traveling, the clue points to AWS Client VPN, not to a site-to-site VPN.

  • «low-cost backup connection for Direct Connect»

    A VPN to the same virtual private gateway kicks in if Direct Connect goes down, without paying for a second dedicated circuit.

    When not: The backup VPN does not offer the same performance. If the backup must match the primary link, AWS recommends a second Direct Connect connection; and for Local Zones, a VPN backup is not supported.

  • «encrypt the traffic that travels over Direct Connect»

    A private IP VPN runs over a Direct Connect transit VIF and terminates on a transit gateway, so traffic is encrypted with IPsec without going out to the internet.

    When not: On supported dedicated connections, MACsec encrypts the link at its own layer and may be the expected answer. And a private IP VPN requires a transit gateway: it cannot be done with a virtual private gateway.

  • «improve VPN performance from sites far from the Region»

    Accelerated Site-to-Site VPN makes traffic enter the AWS global network as soon as possible, with more consistent behavior than the public internet.

    When not: It only exists with a transit gateway, not with a virtual private gateway. And if the problem is link capacity rather than the path over the internet, think of Direct Connect.

  • «exceed the bandwidth of a single VPN tunnel»

    With a transit gateway (or with AWS Cloud WAN) you can use large bandwidth tunnels, up to 5 Gbps instead of 1.25 Gbps. And with a transit gateway you can enable ECMP: traffic is spread across several VPN tunnels and connections, adding up their capacity.

    When not: With a virtual private gateway all VPNs share a single aggregate limit, so adding connections does not add bandwidth. For high, stable capacity, Direct Connect.

Often paired with

  • AWS Transit Gateway
Study AWS Site-to-Site VPN →