Which solution will meet these requirements with the LEAST operational overhead?
Create an RDS manual snapshot. Upgrade to the new version of Amazon RDS for MySQL.
Use native backup and restore. Restore the data to the upgraded new version of Amazon RDS for MySQL.
Use AWS Database Migration Service (AWS DMS) to replicate the data to the upgraded new version of Amazon RDS for MySQL.
Use Amazon RDS Blue/Green Deployments to deploy and test production changes.
Explanations:
While creating a manual snapshot allows for a point-in-time backup of the database, upgrading directly from the snapshot does not allow for testing functionality on the new version without affecting the live environment. If the upgrade encounters issues, the process may lead to downtime.
Native backup and restore involves more manual steps and can lead to longer downtime. Restoring data to an upgraded version means that the production database will be down during the restore process, which does not meet the requirement for minimal operational overhead.
Using AWS DMS for data replication adds complexity and operational overhead. While it allows for migration to a new version, it requires configuring and managing a separate migration task, which can be more resource-intensive and time-consuming than other options.
Amazon RDS Blue/Green Deployments allows for creating a new version of the database in a separate environment. This option enables testing of the upgraded version without impacting the production environment. If the new version functions correctly, traffic can be redirected with minimal operational overhead, ensuring data integrity and quick rollback if necessary.