What should a solutions architect recommend to meet these requirements?
Create a Multi-Region Aurora MySQL DB cluster in us-east-1 and use-west-2. Use an Amazon Route 53 health check to monitor us-east-1 and fail over to us- west-2 upon failure.
Take a snapshot of the DB cluster in us-east-1. Configure an Amazon EventBridge (Amazon CloudWatch Events) rule that invokes an AWS Lambda function upon receipt of resource events. Configure the Lambda function to copy the snapshot to us-west-2 and restore the snapshot in us-west-2 when failure is detected.
Create an AWS CloudFormation script to create another Aurora MySQL DB cluster in us-west-2 in case of failure. Configure an Amazon EventBridge (Amazon CloudWatch Events) rule that invokes an AWS Lambda function upon receipt of resource events. Configure the Lambda function to deploy the AWS CloudFormation stack in us-west-2 when failure is detected.
Recreate the database as an Aurora global database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2. Configure an Amazon EventBridge (Amazon CloudWatch Events) rule that invokes an AWS Lambda function upon receipt of resource events. Configure the Lambda function to promote the DB cluster in us-west-2 when failure is detected.
Explanations:
A Multi-Region Aurora MySQL DB cluster cannot be created in this manner; Aurora Global Database is needed for cross-region replication. Route 53 health checks are not sufficient for automated failover without additional configuration for promoting the secondary cluster.
Taking a snapshot and copying it to the other region would not meet the RTO of 15 minutes. The process of snapshotting, copying, and restoring would take significantly longer than this, leading to unacceptable downtime.
While this approach creates a backup in the second region, deploying the CloudFormation stack upon failure would also likely exceed the 15-minute RTO due to the time it would take to create and configure the new cluster.
Recreating the database as an Aurora global database allows for near real-time replication between regions. In the event of a failure, the secondary cluster in us-west-2 can be promoted quickly to minimize downtime, aligning with the 15-minute RTO requirement.
I classify that the answer is:
Recreate the database as an Aurora global database with the primary DB cluster in us-east-1 and a secondary DB cluster in us-west-2. Configure an Amazon EventBridge (Amazon CloudWatch Events) rule that invokes an AWS Lambda function upon receipt of resource events. Configure the Lambda function to promote the DB cluster in us-west-2 when failure is detected.