Intermediate LevelCloud Computing (AWS/GCP/Azure)
What is the difference between AWS Direct Connect and Site-to-Site VPN?
❓ Interview Prompt: Compare AWS Direct Connect (dedicated physical fiber, low latency) vs AWS Site-to-Site IPsec VPN (public internet).
Connecting an on-premise data center to AWS VPCs uses two primary hybrid networking options:
1. AWS Site-to-Site VPN:
•
Transport: Encrypted IPsec tunnel established over the public internet.
•
Bandwidth & Latency: Up to 1.25 Gbps per tunnel. Latency fluctuates based on public internet routing.
•
Setup Time: Fast (minutes to hours).
2. AWS Direct Connect (DX):
•
Transport: Dedicated private physical fiber-optic connection from on-premise data centers to an AWS Direct Connect Location.
•
Bandwidth & Latency: Dedicated 1Gbps, 10Gbps, or 100Gbps links with consistent, ultra-low latency.
•
Setup Time: Slow (requires physical telecom circuit installation).
Code Implementation Example
hcl
# AWS Direct Connect Private Virtual Interface (VIF) Configuration
resource "aws_dx_private_virtual_interface" "onprem" {
connection_id = "dxcon-fg5678gh"
name = "onprem-private-vif"
vlan = 4094
asn = 65000
amazon_side_asn = 64512
address_family = "ipv4"
}💡Terraform AWS Direct Connect Private Virtual Interface configuration.
🎯 Interview Key Takeaway
Site-to-Site VPN uses IPsec tunnels over the public internet; Direct Connect provides dedicated private physical fiber connections.
#Direct Connect#VPN#Hybrid Cloud#Networking#Intermediate
Back to all Cloud Computing (AWS/GCP/Azure) Questions→