An enterprise runs a critical payment processing application across two AWS accounts within an AWS Organization. The database layer consists of an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 (Account A) and a secondary cluster in us-west-2 (Account A). The application compute tier runs on Amazon ECS Fargate inside a VPC in us-east-1 (Account B) and a VPC in us-west-2 (Account B). A shared Route 53 Private Hosted Zone (PHZ) named service.internal is hosted in a third Shared Services account (Account C) to resolve internal API endpoints. The business requires a disaster recovery (DR) solution with a Recovery Time Objective (RTO) of under 10 minutes and a Recovery Point Objective (RPO) of under 1 minute. During a simulated complete failure of the us-east-1 region, the operations team performs a manual failover by promoting the Aurora secondary cluster in us-west-2 and updating Route 53 Application Recovery Controller (Route 53 ARC) routing controls. However, the ECS tasks in us-west-2 fail to connect to the database or resolve other internal service endpoints. Additionally, outbound payment API calls fail whenever Availability Zone us-west-2a experiences a localized outage, even though the application tasks are running in multiple Availability Zones. Which combination of actions will resolve these issues and satisfy the disaster recovery requirements?
- Submit a VPC association authorization from the Shared Services account (Account C) for the us-west-2 VPC in Account B, and associate the Private Hosted Zone using the AWS CLI, SDK, or Console. Deploy a NAT Gateway in each Availability Zone utilized by the us-west-2 VPC, and configure the private route tables to route local outbound traffic through the NAT Gateway in the corresponding Availability Zone.Answer
- BShare the Route 53 Private Hosted Zone from the Shared Services account (Account C) with Account B using AWS Resource Access Manager (RAM). Deploy a single NAT Gateway in Availability Zone us-west-2a, and configure a Route 53 failover record to dynamically update VPC route tables to target the NAT Gateway in another Availability Zone during an outage.
- CRe-create a duplicate Private Hosted Zone named service.internal directly in Account B and associate it with the us-west-2 VPC. Deploy a single NAT Gateway in Availability Zone us-west-2a, and configure the private route tables of all subnets across all Availability Zones in us-west-2 to target this single NAT Gateway to minimize standby infrastructure costs.
- DSubmit a VPC association authorization from the Shared Services account (Account C) for the us-west-2 VPC in Account B, and associate the Private Hosted Zone. Deploy a NAT Gateway in each Availability Zone of the us-west-2 VPC, and configure a Route 53 Active-Passive failover routing policy to redirect outbound database queries back to the us-east-1 database endpoint if latency increases.