A financial services firm hosts a critical transactional application on AWS. The application runs on Amazon ECS tasks on AWS Fargate in the us-east-1 Region, across three Availability Zones. The tasks connect to an Amazon Aurora MySQL database cluster in the same Region. Outbound traffic to external payment processors is routed through a single NAT Gateway located in one of the public subnets.
The firm needs to enhance the reliability of the system and establish a disaster recovery (DR) strategy in the us-west-2 Region. The DR solution must support a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. Additionally, the outbound connectivity in the primary Region must be highly resilient against Availability Zone failures.
Which TWO actions should the Solutions Architect take to meet these 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 tasks on AWS Fargate in us-west-2 at a minimum scale, and set up Amazon Route 53 Application Recovery Controller (ARC) routing controls to manage failover.Answer
- Deploy a NAT Gateway in each Availability Zone within the primary Region, and update the private subnet route tables to route outbound internet traffic through the NAT Gateway in their respective Availability Zone.Answer
- CSet up a cross-Region Aurora replica in the secondary Region, and schedule daily database backups. Upon failover, restore the database from the backup to achieve the lowest cost solution.
- DImplement a Route 53 active-passive failover routing policy pointing to Application Load Balancers in both Regions, disabling Route 53 health checks on the primary record to prevent false failover triggers.
- EMaintain the single NAT Gateway configuration in the primary Region, and configure all private subnet route tables to use this gateway to simplify network architecture and reduce costs.
- FDeploy a Route 53 Private Hosted Zone for database endpoint resolution, but do not associate it with the standby VPC in us-west-2 to avoid cross-VPC DNS resolution overhead.