Question

A company is migrating a 40 TB self-managed MySQL 8.0 database from an on-premises data center to Amazon Aurora MySQL-Compatible Edition. The data center has a 500 Mbps internet connection that is shared with production traffic, and the business requires that ongoing changes be captured and applied so that final cutover downtime is under 15 minutes. The migration team wants to minimize impact on the shared network link during the initial bulk load while still meeting the low-downtime requirement. Which approach best meets these requirements?

Accepted Answer

Export the full database to an AWS Snowball Edge device for the initial bulk load, then use a single AWS DMS task with change data capture (CDC) over the network to replicate ongoing changes until cutover.

Answer

Run a single AWS DMS full-load-plus-CDC task entirely over the existing 500 Mbps internet connection and schedule the full load during a maintenance window.

Answer

Use AWS DataSync to copy the raw MySQL data files to Amazon S3, then restore them directly into Aurora and enable binlog replication for ongoing changes.

Answer

Use AWS Application Migration Service (MGN) to rehost the database server as an EC2 instance, then convert it to Aurora after cutover.