A company operates a microservices application split across two VPCs (VPC A and VPC B) in the same AWS Region. VPC A hosts the front-end API gateway, and VPC B hosts the backend database services. Approximately of data is transferred monthly between VPC A and VPC B. Currently, the VPCs are connected using an AWS Transit Gateway, which has caused a significant increase in the monthly AWS bill due to data processing charges. Which of the following strategies should a SysOps administrator implement to minimize data transfer costs while keeping the traffic entirely within the AWS private network? (Select TWO.)
- Establish a VPC Peering connection between VPC A and VPC B, and route the traffic between the VPCs through the peering connection.Answer
- Ensure that the resources in VPC A and VPC B that communicate with each other are deployed in the same Availability Zone.Answer
- CDeploy NAT Gateways in each Availability Zone of VPC A and VPC B, and route the traffic between VPCs through the NAT Gateways.
- DCreate an Interface VPC Endpoint (AWS PrivateLink) in VPC A pointing to a Network Load Balancer in VPC B, and route all traffic through the endpoint.
- EConfigure a Gateway Load Balancer endpoint in VPC A to distribute traffic to the backend database instances in VPC B.
Answer
Establish a VPC Peering connection between VPC A and VPC B, and ensure that the resources in VPC A and VPC B that communicate with each other are deployed in the same Availability Zone.
Establishing a VPC Peering connection eliminates the per GB AWS Transit Gateway data processing charges since VPC Peering has no processing fees. Furthermore, ensuring that communicating resources are deployed in the same Availability Zone eliminates the cross-AZ data transfer charge of per GB, reducing the data transfer cost for this traffic to zero.
Step-by-Step Solution
Key Concept
Minimizing AWS intra-region data transfer costs by using VPC Peering instead of Transit Gateway and matching Availability Zones to avoid cross-AZ fees.
Estimated Time:1m 30s