A company has three VPCs in the us-east-1 Region: a production VPC, a shared services VPC, and a data analytics VPC. Currently, the VPCs are interconnected using an AWS Transit Gateway. The data analytics team reports that transferring large datasets between the production VPC and the data analytics VPC is experiencing throughput bottlenecks and higher-than-expected latency. Which solution will provide the highest throughput and lowest latency for inter-VPC traffic?
- AConfigure an AWS Direct Connect gateway to route transitive traffic between the production VPC and the data analytics VPC.
- Establish a direct VPC Peering connection between the production VPC and the data analytics VPC, and update the VPC route tables to route traffic through the peering connection.Answer
- CDeploy a single NAT Gateway in the shared services VPC and route the data transfer traffic over the public internet.
- DAssociate a Route 53 Private Hosted Zone with all VPCs and configure latency-based routing records pointing to public IP addresses.
Answer
Establish a direct VPC Peering connection between the production VPC and the data analytics VPC, and update the VPC route tables to route traffic through the peering connection.
Establishing a direct VPC Peering connection provides a point-to-point network path with the lowest latency and no bandwidth limitations. While AWS Transit Gateway is excellent for managing multi-VPC spoke topologies, it adds a small latency hop and has default bandwidth limitations per connection. Point-to-point VPC Peering between the high-throughput VPCs resolves the bottleneck.
Step-by-Step Solution
Key Concept
VPC Peering vs. AWS Transit Gateway Latency and Throughput Characteristics
Estimated Time:1m 0s