A solutions architect is planning the migration of an on-premises MySQL database to an Amazon Aurora MySQL-Compatible Edition DB cluster. The migration must minimize application downtime, so the architect decides to use AWS Database Migration Service (AWS DMS) with a Full Load plus Ongoing Replication (CDC) task. The source database is highly active. During testing, the CDC replication task fails shortly after starting because updates and deletes on the source cannot be fully resolved by the replication task. Which configuration must be applied to the source MySQL database to resolve this issue and support continuous replication?
- Configure the source database to use ROW-based binary logging format and set the binary log row image parameter (binlog_row_image) to FULL.Answer
- BConfigure the source database to use STATEMENT-based binary logging and set the binary log checksum parameter to CRC32.
- CConfigure the source database to use MIXED-based binary logging and enable Global Transaction Identifiers (GTIDs) for replication.
- DConfigure the source database to use ROW-based binary logging and call the mysql.rds_set_configuration procedure to set the binary log retention hours to 24.
Answer
Configure the source database to use ROW-based binary logging format and set the binary log row image parameter (binlog_row_image) to FULL.
Configuring the source MySQL database to use ROW-based binary logging format (`binlog_format = ROW`) and setting the binary log row image parameter (`binlog_row_image = FULL`) is a mandatory prerequisite for AWS DMS Change Data Capture (CDC) from a MySQL source. This ensures that the binary logs contain complete information about before and after states for update and delete events, allowing the DMS replication task to apply the changes to the target database.
Step-by-Step Solution
Key Concept
AWS DMS MySQL Source CDC Prerequisites