A flight booking aggregator application hosts its primary infrastructure in the us-east-1 Region. The architecture consists of Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and a Multi-AZ Amazon RDS for MySQL database. The company needs to design a cross-region disaster recovery (DR) plan to a secondary AWS region. The DR solution must achieve a Recovery Time Objective (RTO) of hours and a Recovery Point Objective (RPO) of minutes while minimizing ongoing infrastructure running costs. Which solution meets these requirements?
- AConfigure the RDS database with Multi-AZ deployment and use an Auto Scaling group across multiple Availability Zones in the primary region. Configure Amazon Route 53 latency routing to automatically direct traffic.
- Configure a cross-region read replica of the RDS database in the secondary region. Store pre-baked AMIs of the EC2 instances in both regions. In the event of a disaster, promote the read replica to a standalone database and launch the EC2 instances in the secondary region using the AMIs.Cevap
- CExport database backups every minutes to Amazon S3 Glacier Flexible Retrieval and configure S3 Cross-Region Replication to copy the backups to the secondary region. In the event of a disaster, retrieve the backups from Glacier to restore the database and launch the EC2 instances.
- DDeploy a scaled-down active version of the application stack, including a running, smaller RDS database instance and an active EC2 instance in the secondary region, and scale up the environment during a failover event.
Cevap
The correct solution configures a cross-region read replica of the RDS database to meet the RPO and stores pre-baked AMIs to launch EC2 instances in the secondary region during a disaster to meet the RTO while minimizing ongoing costs.
The correct solution uses a Pilot Light disaster recovery strategy. Creating a cross-region read replica of the Amazon RDS database ensures that data is continuously replicated asynchronously to the secondary region, which achieves a Recovery Point Objective (RPO) of minutes, well within the -minute limit. Storing pre-baked AMIs of the EC2 instances allows them to be launched quickly during a failover event, which easily meets the Recovery Time Objective (RTO) of hours. Because the EC2 instances are not running in the secondary region until a disaster occurs, this approach minimizes ongoing infrastructure running costs.
Adım Adım Çözüm
Anahtar Kavram
AWS Disaster Recovery Strategies: Pilot Light vs. Warm Standby