Which solution will meet these requirements?
Configure the EC2 instances to use AWS Elastic Disaster Recovery. Create a cross-Region read replica for the RDS DB instance. Create an ALB in a second AWS Region. Create an AWS Global Accelerator endpoint, and associate the endpoint with the ALBs. Update DNS records to point to the Global Accelerator endpoint.
Configure the EC2 instances to use Amazon Data Lifecycle Manager (Amazon DLM) to take snapshots of the EBS volumes. Configure RDS automated backups. Configure backup replication to a second AWS Region. Create an ALB in the second Region. Create an AWS Global Accelerator endpoint, and associate the endpoint with the ALBs. Update DNS records to point to the Global Accelerator endpoint.
Create a backup plan in AWS Backup for the EC2 instances and RDS DB instance. Configure backup replication to a second AWS Region. Create an ALB in the second Region. Configure an Amazon CloudFront distribution in front of the ALB. Update DNS records to point to CloudFront.
Configure the EC2 instances to use Amazon Data Lifecycle Manager (Amazon DLM) to take snapshots of the EBS volumes. Create a cross-Region read replica for the RDS DB instance. Create an ALB in a second AWS Region. Create an AWS Global Accelerator endpoint, and associate the endpoint with the ALBs.
Explanations:
This option uses AWS Elastic Disaster Recovery to ensure quick recovery of the EC2 instances, providing a low RPO and RTO. The cross-Region read replica for RDS allows for a rapid failover for the database, meeting its RPO and RTO requirements. Using AWS Global Accelerator optimizes latency and ensures seamless traffic management between regions.
While this option uses Amazon Data Lifecycle Manager for EBS snapshots and RDS automated backups, it does not specifically address the RPO and RTO requirements effectively. Automated backups may not provide the required RPO and RTO without additional measures. Additionally, using only snapshots may lead to longer recovery times.
Although creating a backup plan with AWS Backup is a good practice, this option does not address RPO and RTO requirements directly. It also suggests using CloudFront in front of the ALB, which is more suited for content delivery rather than disaster recovery, thus failing to ensure optimal latency during failover.
This option configures EBS snapshots and a cross-Region read replica for the RDS instance, which helps with recovery, but it does not specify using a disaster recovery service for the EC2 instances, potentially leading to longer RTO. It also lacks the latency optimization provided by Global Accelerator, making it less suitable for the requirements.
I outline that the answer is:
Configure the EC2 instances to use AWS Elastic Disaster Recovery. Create a cross-Region read replica for the RDS DB instance. Create an ALB in a second AWS Region. Create an AWS Global Accelerator endpoint, and associate the endpoint with the ALBs. Update DNS records to point to the Global Accelerator endpoint.