Using Microsoft Azure Database for MySQL flexible server as a source for Amazon DMS - Amazon Database Migration Service
Limitations when using Azure MySQL as a source for Amazon Database Migration Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Using Microsoft Azure Database for MySQL flexible server as a source for Amazon DMS

With Amazon DMS, you can use Microsoft Azure Database for MySQL flexible server as a source in much the same way as you do MySQL.

For information about versions of Microsoft Azure Database for MySQL flexible server that Amazon DMS supports as a source, see Sources for Amazon DMS.

For more information about using a customer-managed MySQL-compatible database with Amazon DMS, see Using a self-managed MySQL-compatible database as a source for Amazon DMS.

Limitations when using Azure MySQL as a source for Amazon Database Migration Service

  • The defaut value for the Azure MySQL flexible server system variable sql_generate_invisible_primary_key is ON, and the server automatically adds a generated invisible primary key (GIPK) to any table that is created without an explicit primary key. Amazon DMS doesn’t support ongoing replication for MySQL tables with GIPK constraints.