An enterprise operates a multi-VPC architecture in the `eu-west-1` Region. An ETL application running on Amazon EC2 instances in VPC A (Production) regularly extracts large datasets from an RDS MySQL database and transfers of data monthly to an Amazon Redshift cluster in VPC B (Analytics). Currently, all inter-VPC traffic is routed through an AWS Transit Gateway. A solutions architect is tasked with optimizing the network design to reduce monthly data transfer costs without introducing network performance bottlenecks. Which routing strategy is the most cost-effective?
- Establish a VPC Peering connection between VPC A and VPC B, and update the route tables in both VPCs to route the database traffic through the peering connection.Cevap
- BDeploy NAT Gateways in the private subnets of VPC A and VPC B, and configure the application to transfer the data over the public internet.
- CConfigure an AWS Site-to-Site VPN connection between the two VPCs using Virtual Private Gateways, and route the database traffic through the IPsec tunnels.
- DCreate an AWS PrivateLink endpoint service for the Amazon Redshift cluster in VPC B, and provision an interface VPC endpoint in VPC A to transfer the data.
Cevap
Establish a VPC Peering connection between VPC A and VPC B, and update the route tables in both VPCs to route the database traffic through the peering connection.
Establishing a VPC Peering connection directly between VPC A and VPC B is the most cost-effective solution. VPC Peering does not charge hourly fees or data processing fees. It only charges standard intra-region data transfer rates (which are free within the same Availability Zone or cost 120\text{ TB} 0.02 per GB Transit Gateway data processing fee, saving monthly.
Adım Adım Çözüm
Anahtar Kavram
Selecting the most cost-effective network routing mechanism based on data volume, where VPC Peering is preferred over AWS Transit Gateway and AWS PrivateLink for high-volume traffic due to the absence of per-GB data processing fees.