A logistics company is migrating its core shipment tracking system to AWS. The application uses a PostgreSQL database and must be resilient to a complete AWS Region outage. The solutions architect must design a disaster recovery (DR) strategy with a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 10 seconds. Which configuration meets these requirements with the least operational overhead?
- Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region, using cross-Region replication.Cevap
- BDeploy an Amazon RDS for PostgreSQL DB instance with a cross-Region Read Replica, and configure an AWS Lambda function to automatically promote the replica during an outage.
- CDeploy an Amazon RDS for PostgreSQL DB instance with Multi-AZ enabled, and configure Route 53 latency-based routing to automatically fail over to a standby instance in the secondary Region.
- DDeploy an Amazon Aurora PostgreSQL DB cluster in the primary Region and set up AWS Backup to copy snapshots to the secondary Region every 15 minutes, restoring them in the event of a disaster.
Cevap
Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region, using cross-Region replication.
The correct configuration uses Amazon Aurora Global Databases, which feature built-in, storage-based replication across AWS Regions. It achieves an RPO of less than 10 seconds because replication lag is typically less than one second. The secondary cluster can be promoted to a primary cluster with full read/write capabilities in less than 15 minutes, satisfying the RTO requirement with minimal operational overhead.
Adım Adım Çözüm
Anahtar Kavram
Disaster recovery replication and failover constraints for managed relational databases on AWS