An enterprise has a critical order-processing application deployed in AWS. The current architecture runs in a single AWS Region across multiple Availability Zones, utilizing an Application Load Balancer (ALB), an Auto Scaling group of Amazon EC2 instances, and an Amazon Aurora PostgreSQL Global Database with a primary cluster in us-east-1 and a secondary read-only cluster in us-west-2. Route 53 is used for DNS routing with simple routing records pointing to the us-east-1 ALB. During a recent regional outage in us-east-1, the operations team suffered significant recovery delays because the Route 53 DNS records had to be updated manually. Additionally, internal microservices in the secondary VPC failed to resolve internal endpoints because the Route 53 Private Hosted Zone (PHZ) was not accessible, and the application's database connection pool crashed because the database endpoint names changed. The company requires a disaster recovery strategy that provides an Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute. Which of the following solutions should a Solutions Architect implement to meet these requirements with the least operational complexity?
- AConfigure Route 53 Application Recovery Controller (ARC) routing controls for regional failover. Create a new Route 53 Private Hosted Zone in the us-west-2 VPC with the same domain name as the primary region to manage internal service discovery locally. Configure AWS Lambda triggered by an Amazon EventBridge rule to promote the secondary Aurora cluster.
- BConfigure Route 53 failover routing pointing to the ALBs in both regions. Rely on Route 53 DNS failover based on ALB health checks to automatically shift traffic. Configure Aurora cross-region read replicas in us-west-2, and configure the database client library connection string to automatically promote the read replica to primary when the primary database becomes unresponsive.
- Configure Route 53 Application Recovery Controller (ARC) routing controls to manage failover between the ALBs in both regions. Associate the Route 53 Private Hosted Zone in the primary account with the VPC in us-west-2. Use an AWS Systems Manager Automation runbook to promote the secondary Aurora cluster using the failover-global-cluster command and update a Route 53 CNAME record pointing to the promoted database endpoint.Cevap
- DReconfigure the disaster recovery architecture to use a Pilot Light strategy. Set up AWS Backup to replicate EBS snapshots of the EC2 instances and Aurora snapshots to us-west-2 daily. During an outage, use AWS CloudFormation to provision the ALB and Auto Scaling group, and restore the Aurora cluster from the copied snapshot.