A financial technology company is designing a new multi-region disaster recovery and high availability architecture for its core payment reconciliation service. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and utilizes an Amazon Aurora PostgreSQL database. The application must communicate with external payment gateways over the internet to perform verification. The business requirements specify a Recovery Time Objective (RTO) of 15 minutes, a Recovery Point Objective (RPO) of 2 minutes, and high availability within the primary region. Which of the following architectures meets these requirements with the lowest operational complexity?
- Deploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with Failover routing policies and active Application Load Balancer health checks to route public user traffic to the primary region.Cevap
- BDeploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, but route all outbound traffic through a single NAT Gateway in one Availability Zone to reduce costs. Configure Route 53 with Failover routing policies and active Application Load Balancer health checks.
- CDeploy the application in a primary AWS Region. Configure Amazon Aurora to automatically copy database snapshots to a secondary AWS Region every 4 hours. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with Failover routing to direct users to the primary region, and restore the database from the secondary region snapshot during a failover event.
- DDeploy the application in a primary AWS Region and a secondary AWS Region. Use Amazon Aurora Global Database to replicate data to the secondary region. In the primary region, deploy the EC2 instances across multiple Availability Zones, with a NAT Gateway in each Availability Zone. Configure Route 53 with a Private Hosted Zone to perform failover routing of public client requests to the secondary region during an outage.
Cevap
Deploy the application in primary and secondary regions, using Amazon Aurora Global Database for replication. Ensure outbound connectivity in the primary region is resilient by placing a NAT Gateway in each Availability Zone, and use Route 53 Failover routing with public Application Load Balancer health checks to handle region failover.
The configuration that deploys the application across two regions with Amazon Aurora Global Database satisfies the strict 2-minute RPO because Aurora Global Database replicates data in under a second. The 15-minute RTO is met via Route 53 Failover routing to direct public traffic to the primary region and fail over to the secondary region if a disaster occurs. Deploying a NAT Gateway in each Availability Zone ensures that outbound payment gateway communication remains highly available within the primary region.
Adım Adım Çözüm
Anahtar Kavram
Disaster recovery architectures require aligning database replication (RPO), networking redundancy (HA), and public DNS routing (RTO) to eliminate single points of failure both within and across AWS regions.