An enterprise operates a critical inventory orchestration system across a multi-account AWS Organization. The compute tier runs on Amazon EC2 instances in private subnets in a primary Workload account VPC in the us-east-1 Region, spread across three Availability Zones. This tier processes messages and sends outbound API updates to external suppliers. The database tier is an Amazon Aurora MySQL DB cluster in the same VPC. The compute tier resolves the database endpoint using a Route 53 Private Hosted Zone (PHZ) (internal.inventory.local) hosted in a separate Shared Services account.
The company wants to enhance the disaster recovery (DR) posture by deploying a warm standby solution in us-west-2. The business requires a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes. The outbound API connections must remain highly reliable and fault-tolerant during a regional outage.
Which combination of architectural modifications meets these requirements according to AWS best practices?
- Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the standby compute tier in a new VPC in us-west-2 across three Availability Zones, configuring a NAT Gateway in each Availability Zone for outbound supplier updates. Submit a VPC association authorization from the Shared Services account for the us-west-2 VPC, and associate the internal.inventory.local PHZ using the Workload account credentials. Use AWS Route 53 Application Recovery Controller routing controls to manage failover, promoting the secondary Aurora cluster to primary and redirecting application traffic.Cevap
- BConfigure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the standby compute tier in a new VPC in us-west-2 across three Availability Zones, with all private subnets routing outbound traffic through a single NAT Gateway in a single Availability Zone. Rely on Transit Gateway peering between the regions to transitively route DNS queries for internal.inventory.local from the us-west-2 VPC to the Route 53 Resolver in the us-east-1 VPC without performing cross-account PHZ association. Perform a managed failover of the Aurora Global Database during a disaster event.
- CConfigure AWS Backup to take hourly copy-replicated snapshots of the Aurora database cluster and daily Amazon Machine Images (AMIs) of the EC2 instances, replicating them to us-west-2. Deploy the standby compute tier in a new VPC in us-west-2 across three Availability Zones, configuring a NAT Gateway in each Availability Zone. Submit a VPC association authorization from the Shared Services account for the us-west-2 VPC, and associate the internal.inventory.local PHZ using the Workload account credentials. In the event of an outage, use an AWS Lambda function to restore the database from the latest snapshot and launch EC2 instances from the AMIs.
- DConfigure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy the standby compute tier in a new VPC in us-west-2 across three Availability Zones, configuring a NAT Gateway in each Availability Zone. Submit a VPC association authorization from the Shared Services account for the us-west-2 VPC, and associate the internal.inventory.local PHZ using the Workload account credentials. Configure a Route 53 failover routing policy in the PHZ for the database DNS record pointing to both regional endpoints, and associate the primary record with a standard Route 53 health check targeting the primary database's private IP address on the database port.