An enterprise runs a media transcoding application on Amazon ECS tasks (AWS Fargate) in a multi-AZ VPC in the us-east-1 Region. The application uses an Amazon Aurora PostgreSQL database cluster for metadata storage. Internal microservices communicate within the VPC using private DNS names registered in a Route 53 Private Hosted Zone (PHZ).
To enhance reliability, a solutions architect must design a disaster recovery (DR) solution in the us-west-2 Region. The solution must achieve a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 2 minutes.
Which set of actions should the solutions architect take to meet these disaster recovery requirements?
- Configure Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Pre-deploy the Amazon ECS service in us-west-2 with a minimum task count of 1. Associate the existing Route 53 Private Hosted Zone with the VPC in us-west-2, and configure Route 53 failover routing records with active health checks associated with the primary Application Load Balancer.Cevap
- BConfigure Amazon Aurora cross-region read replicas to replicate metadata to us-west-2. Implement a pilot light strategy by deploying the Amazon ECS service via AWS CloudFormation templates in us-west-2 with the task count set to 0. During a failover event, update the task count to scale out the ECS service and associate the Route 53 Private Hosted Zone with the us-west-2 VPC.
- CConfigure Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Pre-deploy the Amazon ECS service in us-west-2 with a minimum task count of 1. Associate the Route 53 Private Hosted Zone with the VPC in us-west-2. Set up Route 53 failover routing records pointing to the primary and secondary Application Load Balancers, but configure the records without Route 53 health checks, relying on manual DNS updates to route traffic during a failover event.
- DConfigure Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Pre-deploy the Amazon ECS service in us-west-2 with a minimum task count of 1. Configure Route 53 failover routing records with active health checks on the primary Application Load Balancer, but keep the Route 53 Private Hosted Zone associated only with the us-east-1 VPC to prevent DNS naming conflicts.
Cevap
The correct strategy involves configuring Amazon Aurora Global Database, pre-deploying a warm standby Amazon ECS service in the secondary region, associating the Private Hosted Zone with both VPCs, and using Route 53 failover routing with active health checks.
The correct architecture leverages Amazon Aurora Global Database, which offers cross-region replication with an RPO of under 1 second, easily meeting the 2-minute RPO requirement. By pre-deploying the Amazon ECS service with a minimum task count of 1 in the standby region (warm standby), the system can handle initial traffic immediately, satisfying the 15-minute RTO requirement. Associating the Route 53 Private Hosted Zone with the VPCs in both regions enables seamless private DNS resolution for internal microservices when traffic fails over. Configuring Route 53 failover routing records with active health checks on the primary Application Load Balancer enables automated failover to the standby region if the primary region experiences an outage.
Adım Adım Çözüm
Anahtar Kavram
Multi-region disaster recovery, database replication latency, and Private Hosted Zone cross-VPC association.
Tahmini Süre:2m 0s