A company's production database runs on an Amazon RDS for PostgreSQL DB instance. A SysOps Administrator must establish a cross-Region disaster recovery (DR) solution that guarantees a Recovery Point Objective (RPO) of less than 30 minutes and a Recovery Time Objective (RTO) of less than 15 minutes. Which strategy should the administrator implement to meet these requirements?
- AEnable Multi-AZ deployment for the DB instance and specify the disaster recovery Region as the secondary Availability Zone to automate synchronous replication and failover.
- BConfigure Amazon S3 Cross-Region Replication (CRR) to replicate the automated DB snapshots from the source Region's automated backup bucket to a destination bucket, without enabling S3 versioning on either bucket.
- Create a cross-Region Read Replica of the DB instance in the disaster recovery Region. During a disaster, promote the Read Replica to a standalone DB instance and update the application endpoint.Answer
- DConfigure a Route 53 active-active failover routing policy between the primary DB instance and a cross-Region Read Replica without health checks, allowing Route 53 to automatically redirect write traffic during a regional outage.
Answer
Create a cross-Region Read Replica of the DB instance in the disaster recovery Region. During a disaster, promote the Read Replica to a standalone DB instance and update the application endpoint.
Creating a cross-Region Read Replica provides asynchronous replication to another AWS Region, which typically keeps replication lag (RPO) to under a few minutes. If a regional disaster occurs, promoting the Read Replica to a standalone DB instance and modifying the application's endpoint is a quick operation that easily fits within the 15-minute RTO.
Step-by-Step Solution
Key Concept
Cross-Region disaster recovery for Amazon RDS using Read Replicas.