A multinational legal services firm is designing a new document e-discovery platform on AWS. The application tier will run on Amazon EC2 instances in private subnets across three Availability Zones in both the primary Region (eu-west-1) and the disaster recovery Region (us-east-1). The EC2 instances must query external court deposition APIs over the public internet to validate filing metadata. The database layer will run on Amazon Aurora PostgreSQL.
The system must meet the following business requirements:
- Recovery Time Objective (RTO) must be less than 10 minutes.
- Recovery Point Objective (RPO) must be less than 1 minute.
- Internal microservices in both Regions must resolve internal database endpoints using a single private hosted zone named corp.discovery.local.
- External user traffic should target the primary Region by default, but fail over automatically to the disaster recovery Region if the primary Region's application tier experiences degraded health.
- Outbound network traffic in each Region must be highly available and resilient to Availability Zone failures.
Which architecture should a solutions architect select to meet these requirements with the lowest operational complexity?
- Deploy an Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in us-east-1. Deploy a NAT Gateway in each Availability Zone in both Regions to handle outbound traffic. Associate the Route 53 Private Hosted Zone corp.discovery.local with the VPCs in both Regions. Configure Route 53 Failover routing for external traffic, pointing the primary record to the eu-west-1 Application Load Balancer (ALB) with an active health check, and the secondary record to the us-east-1 ALB.Cevap
- BDeploy an Amazon Aurora PostgreSQL DB instance in eu-west-1 and configure cross-Region snapshot copies to us-east-1 every 12 hours. Deploy a NAT Gateway in each Availability Zone in both Regions to handle outbound traffic. Associate the Route 53 Private Hosted Zone corp.discovery.local with the VPCs in both Regions. Configure Route 53 Failover routing for external traffic, pointing the primary record to the eu-west-1 Application Load Balancer (ALB) with an active health check, and the secondary record to the us-east-1 ALB.
- CDeploy an Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in us-east-1. Deploy a NAT Gateway in each Availability Zone in both Regions to handle outbound traffic. Create the Route 53 Private Hosted Zone corp.discovery.local and associate it only with the VPC in eu-west-1. Configure Route 53 Failover routing for external traffic, pointing the primary record to the eu-west-1 Application Load Balancer (ALB) with an active health check, and the secondary record to the us-east-1 ALB.
- DDeploy an Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in us-east-1. Deploy a single NAT Gateway in the primary Availability Zone of each Region's VPC to route outbound traffic. Associate the Route 53 Private Hosted Zone corp.discovery.local with the VPCs in both Regions. Configure Route 53 Failover routing for external traffic, pointing the primary record to the eu-west-1 Application Load Balancer (ALB) with an active health check, and the secondary record to the us-east-1 ALB.