An enterprise is migrating a critical, write-heavy core banking application to AWS. The database architecture must satisfy the following resiliency requirements:
- Within the primary AWS region, the database must achieve high availability with zero data loss (Recovery Point Objective, ) and automated failover in less than 30 seconds.
- Across a secondary AWS region, the disaster recovery solution must support active read scaling during normal operations, maintain a cross-region replication lag under 2 seconds ( seconds), and allow failover to the secondary region in less than 5 minutes ( minutes).
Which database configuration meets these requirements with the lowest operational overhead?
- Amazon Aurora PostgreSQL-Compatible Edition with an Aurora Global Database. Deploy the primary cluster in the main region and a secondary cluster in the recovery region, routing read traffic in the secondary region to the local reader instances.Cevap
- BAmazon RDS for PostgreSQL with a Multi-AZ DB instance deployment in the primary region, and a cross-region Read Replica in the secondary region. Use Route 53 Latency Routing to automatically direct database write traffic to the replica in the secondary region if the primary region becomes unavailable.
- CAmazon RDS for PostgreSQL with a Multi-AZ DB instance deployment in the primary region. In the secondary region, configure a pilot light database environment by restoring daily snapshots transferred from the primary region, scale up the instance class only during failover, and direct traffic using Route 53 Failover Routing.
- DAmazon RDS for PostgreSQL with a Single-AZ DB instance deployment in the primary region. Configure an asynchronous cross-region Read Replica in the secondary region, and write a custom AWS Lambda script to monitor primary database health and automatically promote the replica during a regional outage.
Cevap
Amazon Aurora PostgreSQL-Compatible Edition with an Aurora Global Database. Deploy the primary cluster in the main region and a secondary cluster in the recovery region, routing read traffic in the secondary region to the local reader instances.
The correct option implements Amazon Aurora Global Database, which matches all constraints. For local high availability, Aurora replicates data synchronously across three AZs, ensuring and automated failover in less than 30 seconds. For multi-region resilience, storage-based physical replication keeps lag below 2 seconds (typically under 1 second), and secondary clusters can serve active read traffic and be promoted to primary in less than a minute.
Adım Adım Çözüm
Anahtar Kavram
Amazon Aurora Global Databases and Multi-AZ replication