A logistics company is designing a new multi-region web application on AWS for real-time fleet tracking. The application must run in two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. The architecture must minimize ongoing running costs in the secondary region while ensuring that outbound APIs (e.g., to external GPS telemetry providers) remain highly available within the primary region.
Which architecture meets these requirements?
- ADeploy the application in us-east-1 using Application Load Balancers (ALBs) and Auto Scaling Groups (ASGs). Configure a cross-region backup strategy using AWS Backup to copy EBS snapshots and Aurora database snapshots from us-east-1 to us-west-2 once every 24 hours. In the event of a regional disaster in us-east-1, use AWS CloudFormation to deploy the ALBs and ASGs in us-west-2, restore the Aurora database from the copied snapshots, and update Route 53 simple routing records to point to the new load balancer.
- BDeploy the application in us-east-1 (Primary) and us-west-2 (Secondary) using Application Load Balancers (ALBs) and Auto Scaling Groups (ASGs). Set up Amazon Aurora Global Database with the primary writer in us-east-1 and a secondary read replica in us-west-2. Configure Route 53 with Failover routing policies pointing to the ALBs in both regions, and associate Route 53 health checks with the primary ALB. To minimize running costs, deploy a single NAT Gateway in one Availability Zone in the primary region's VPC, routing all outbound API traffic from private subnets across all Availability Zones through it.
- Deploy the application in us-east-1 (Primary) and us-west-2 (Secondary) using Application Load Balancers (ALBs) and Auto Scaling Groups (ASGs). Set up Amazon Aurora Global Database with the primary writer in us-east-1 and a secondary read replica in us-west-2. In us-west-2, set the ASG capacity to minimum scale to reduce standby costs. Configure Route 53 with Failover routing policies pointing to the ALBs in both regions, and associate Route 53 health checks with the primary ALB. Ensure the primary VPC has redundant NAT Gateways deployed across multiple Availability Zones for outbound API connectivity.Cevap
- DDeploy the application in us-east-1 (Primary) and us-west-2 (Secondary) using Application Load Balancers (ALBs) and Auto Scaling Groups (ASGs). Set up Amazon Aurora Global Database with the primary writer in us-east-1 and a secondary read replica in us-west-2. Configure Route 53 with Latency routing policies pointing to the ALBs in both regions, and enable health checks on both endpoints. In the event of a regional outage in us-east-1, Route 53 Latency routing will automatically promote the secondary database cluster in us-west-2 to a writer and redirect all write traffic without operational intervention.
Cevap
Deploying the application in both regions, using Amazon Aurora Global Database for sub-minute data replication, configuring Route 53 Failover routing, running the secondary Auto Scaling Group at minimal scale, and provisioning redundant NAT Gateways across multiple Availability Zones in the primary region.
The correct architecture uses Route 53 Failover routing to direct traffic to the primary region (us-east-1) under normal operation and failover to the secondary region (us-west-2) during an outage. Aurora Global Database provides sub-minute replication to meet the 1-minute RPO. Outbound API high availability is maintained in the primary region by deploying redundant NAT Gateways across multiple Availability Zones. Running the secondary Application Auto Scaling Group at minimal scale satisfies the cost optimization constraint while remaining ready to scale up upon failover.
Adım Adım Çözüm
Anahtar Kavram
Multi-Region Active-Passive (Warm Standby) disaster recovery with Route 53 Failover, Aurora Global Database, and high availability NAT Gateway design.