An advertising technology company runs a real-time bidding application with sub-millisecond processing requirements. The application's front-end bidding engines are deployed in an Ingestion VPC, while the core database cluster is hosted in a separate Processing VPC, both within the `us-east-1` Region. Under peak traffic spikes, the company experiences increased latency and connection timeouts when the bidding engines query the database. The database endpoints are resolved using an Amazon Route 53 Private Hosted Zone (PHZ). The company requires a solution that minimizes latency, avoids additional data processing fees, and ensures high availability across all Availability Zones. How should a solutions architect optimize the network configuration to meet these requirements?
- ADeploy an AWS Transit Gateway and connect both VPCs. Configure the VPC route tables to route all traffic via the Transit Gateway, as it is required to support transitive routing and provides lower latency than VPC Peering.
- BEstablish a VPC Peering connection between the Ingestion VPC and the Processing VPC, and configure the route tables to route database traffic over the peering connection, while keeping the Route 53 Private Hosted Zone associated only with the Processing VPC.
- Establish a VPC Peering connection between the Ingestion VPC and the Processing VPC, configure the routing tables to route database traffic directly over the peering connection, and associate the existing Route 53 Private Hosted Zone with both VPCs.Cevap
- DConfigure the database cluster with public IP addresses, and route database queries from the Ingestion VPC through a single NAT Gateway deployed in a single Availability Zone of the Ingestion VPC to simplify egress routing.