Which solution will meet these requirements with the LEAST operational overhead?
Migrate the MySQL database to multiple EC2 instances. Configure a standby EC2 instance in the DR Region. Turn on replication.
Migrate the MySQL database to Amazon RDS. Use a Multi-AZ deployment. Turn on read replication for the primary DB instance in the different Availability Zones.
Migrate the MySQL database to an Amazon Aurora global database. Host the primary DB cluster in the primary Region. Host the secondary DB cluster in the DR Region.
Store the scheduled backup of the MySQL database in an Amazon S3 bucket that is configured for S3 Cross-Region Replication (CRR). Use the data backup to restore the database in the DR Region.
Explanations:
This option involves manually managing multiple EC2 instances and setting up replication, which increases operational overhead. It lacks built-in high availability and disaster recovery features found in other options.
While Amazon RDS with Multi-AZ provides high availability within a single Region, it does not offer cross-Region replication or DR capabilities. This option would not meet the requirement for a multi-Region DR design.
Amazon Aurora global database allows for cross-Region replication with minimal operational overhead. The primary cluster can be in one Region while the secondary cluster is automatically kept in sync in the DR Region, fulfilling the DR requirement efficiently.
Although storing backups in S3 with Cross-Region Replication allows for disaster recovery, this approach involves manual restoration steps and does not provide real-time replication, making it less efficient and more operationally intensive compared to option C.