An application runs in us-east-1 across three Availability Zones behind an Application Load Balancer, and its MySQL database runs on an Amazon EC2 instance. The company requires a cross-Region disaster recovery design with an RTO under 5 minutes and an RPO under 1 minute. Application servers have been deployed in us-west-2 and Route 53 health checks with DNS failover to us-west-2 are configured. What additional action should the solutions architect take to meet the recovery objectives?

An Amazon Aurora global database is the best solution for meeting the RTO of under 5 minutes and RPO of under 1 minute for cross-Region disaster recovery. Aurora Global Database uses dedicated infrastructure to replicate data with typical RPO of less than 1 second and RTO of less than 1 minute, making it ideal for low-latency, cross-Region recovery. Migrating to Amazon RDS for MySQL with a cross-Region read replica would provide disaster recovery, but promoting a read replica to a standalone instance can take several minutes, potentially exceeding the 5-minute RTO. An RDS Multi-AZ deployment provides high availability within a single Region, but not cross-Region disaster recovery. Creating a MySQL standby database on an EC2 instance in us-west-2 would require manual setup and management of replication, which is more complex and less reliable for achieving strict RPO/RTO targets compared to Aurora Global Database.