Soru

Zorluk: OrtaOptimizing Network Performance and Latency

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?

  1. A
    Deploy 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.
  2. B
    Establish 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.
  3. 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
  4. D
    Configure 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.

Cevap

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.
Establishing a VPC Peering connection provides the lowest latency and highest throughput for inter-VPC traffic within the same region, as it routes traffic directly over the AWS network backbone without passing through intermediate gateways. It also does not charge data processing fees. Associating the Route 53 Private Hosted Zone with both VPCs ensures that resource records for the database are successfully resolved by the client instances in the Ingestion VPC.

Adım Adım Çözüm

1
Create a VPC Peering connection between the Ingestion VPC and the Processing VPC.
The two VPCs are connected directly over the AWS network backbone without routing through intermediate gateways.
VPC Peering provides the lowest latency for same-region inter-VPC traffic and does not charge data processing fees.
2
Update the route tables in both VPCs to target the VPC Peering connection for the destination CIDR blocks.
Traffic between the bidding engines and the database cluster is routed directly over the peering connection.
Route tables must be updated manually for VPC peering connections to enable the flow of traffic.
3
Associate the Route 53 Private Hosted Zone with both the Ingestion VPC and the Processing VPC.
Bidding engines in the Ingestion VPC can resolve the database DNS hostnames to their private IP addresses.
DNS resolution for Private Hosted Zones is limited to associated VPCs; setting up a peering connection does not automatically share DNS resolution.

Anahtar Kavram

Selecting the lowest-latency inter-VPC routing option and configuring cross-VPC DNS resolution.
Tahmini Süre:2m 0s
Bu soruyu puanla