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