During the full load process, AWS DMS as default does not load tables in any particular order, so it might load child table data before parent table data. As a result, foreign key constraints might be violated if they are enabled. Also, if triggers are present on the target database, they might change data loaded by AWS DMS in unexpected ways. To overcome this, we drop the constraints on the target database.
Open MySQL Workbench 8.0 CE from within the EC2 server, and create a new database connection for the target Aurora database using the following values:
|Connection Name||Target Aurora RDS (MySQL)|
After you receive a message stating “Successfully made the MySQL connection”, click OK.
Click on the Target Aurora RDS (MySQL) from the list of MySQL Connections in SQL Workbench to connect to the target database.
In this step you are going to drop the foreign key constraint from the target database: