An enterprise runs an analytics application on Amazon EC2 instances in private subnets across two VPCs: VPC B and VPC C. The application queries a central database cluster hosted in a private subnet within VPC A. Every month, the application in VPC B transfers of data from VPC A, and the application in VPC C transfers of data from VPC A. Currently, all three VPCs are interconnected using an AWS Transit Gateway, which is also connected to an on-premises data center via an AWS Direct Connect Gateway. Which solution represents the most cost-effective network routing architecture to minimize data transfer costs while maintaining the existing Direct Connect hybrid connectivity?
- AConfigure public IP addresses for the database instances in VPC A, and route all database queries from VPC B and VPC C through their respective NAT Gateways to the public IPs of VPC A.
- BReplace the Transit Gateway with a Transit VPC design using software VPN appliances in a central VPC, and establish Site-to-Site VPN connections from VPC A, VPC B, and VPC C to route all database query traffic.
- Establish VPC Peering connections between VPC A and VPC B, and between VPC A and VPC C. Update the route tables in all VPCs to direct the database query traffic over the VPC Peering connections, while continuing to route on-premises and low-volume inter-VPC traffic through the Transit Gateway.Cevap
- DProvision an AWS Managed NAT Gateway in VPC A and configure the database cluster to route all outbound responses to VPC B and VPC C via the NAT Gateway, while keeping Transit Gateway as the connection path.
Cevap
Establish VPC Peering connections between VPC A and VPC B, and between VPC A and VPC C. Update the route tables in all VPCs to direct the database query traffic over the VPC Peering connections, while continuing to route on-premises and low-volume inter-VPC traffic through the Transit Gateway.
The correct solution uses VPC Peering to route high-volume database query traffic ( monthly) directly between VPCs. Since VPC Peering does not charge a data processing fee, this completely avoids the 150,000 \text{ GB} \times \ per month. Keeping the existing Transit Gateway configuration for on-premises connectivity (Direct Connect) and low-volume inter-VPC communication maintains the simplified routing architecture for hybrid traffic without needing full-mesh peering.
Adım Adım Çözüm
Anahtar Kavram
Hybrid VPC routing cost optimization using VPC Peering for high-volume traffic paths combined with AWS Transit Gateway for low-volume and on-premises traffic.
Tahmini Süre:3m 0s