AWS dms documentation change
Summary
Added five new premigration assessment checks for MySQL migration tasks: row size limit for batch apply, target endpoint not being a read replica, table count limit, binary logging enabled, and connection to a MySQL primary instance.
Security assessment
The changes add routine validation checks for migration configuration and compatibility. There is no mention of addressing a specific security vulnerability, weakness, or incident. The checks are focused on ensuring successful migration operations (e.g., avoiding migration failures due to row size limits, ensuring write access to target, managing scale, and enabling required logging).
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MySQL.md b/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MySQL.md index fdf20d076..f2521c620 100644 --- a//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MySQL.md +++ b//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MySQL.md @@ -7 +7 @@ -Validate if Binary Log transaction compression is disabledValidate if DMS user has REPLICATION CLIENT and REPLICATION SLAVE permissions for the source databaseValidate if DMS user has SELECT permissions for the source database tablesValidate if the server_id is set to 1 or greater in the source databaseValidate if DMS user has necessary permissions for the MySQL database as a targetValidate if automatic removal of binary logs is set for the source databaseValidate that limited LOB mode only is used when BatchApplyEnabled is set to trueValidate if a table uses a storage engine other than InnodbValidate if auto-increment is enabled on any tables used for migrationValidate if the database binlog image is set to FULL to support DMS CDCValidate if the source database is a MySQL Read-ReplicaValidate if a table has partitions, and recommend target_table_prep_mode for full-load task settingsValidate if DMS supports the database versionValidate if the target database is configured to set local_infile to 1Validate if target database has tables with foreign keysValidate if source tables in the task scope have cascade constraintsValidate if the timeout values are appropriate for a MySQL source or targetValidate max_statement_time database parameterValidate if Primary Key or Unique Index exist on target for Batch ApplyValidate if both Primary Key and Unique index exist on target for Batch ApplyValidate if secondary indexes are enabled during full load on the target databaseValidate if table has primary key or unique index when DMS validation is enabledRecommendation on using MaxFullLoadSubTasks settingCheck Transformation Rule for Digits RandomizeCheck Transformation Rule for Digits maskCheck Transformation Rule for Hashing maskVerify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneouslyCheck if source Amazon Aurora MySQL instance is not a read replicaCheck if binary log retention time is set properlyCheck if source tables do not have invisible columns.Validate if the database binlog format is set to ROW to support DMS CDCValidate that at least one selected object exists in the source databaseValidate that tables with generated columns exist in the source databaseValidate that skipTableSuspensionForPartitionDdl is enabled for partitioned tablesValidate that max_allowed_packet size can handle source LOB columnsValidate that secondary constraints and indexes (non-primary) are present in the source database +Validate if Binary Log transaction compression is disabledValidate if DMS user has REPLICATION CLIENT and REPLICATION SLAVE permissions for the source databaseValidate if DMS user has SELECT permissions for the source database tablesValidate if the server_id is set to 1 or greater in the source databaseValidate if DMS user has necessary permissions for the MySQL database as a targetValidate if automatic removal of binary logs is set for the source databaseValidate that limited LOB mode only is used when BatchApplyEnabled is set to trueValidate if a table uses a storage engine other than InnodbValidate if auto-increment is enabled on any tables used for migrationValidate if the database binlog image is set to FULL to support DMS CDCValidate if the source database is a MySQL Read-ReplicaValidate if a table has partitions, and recommend target_table_prep_mode for full-load task settingsValidate if DMS supports the database versionValidate if the target database is configured to set local_infile to 1Validate if target database has tables with foreign keysValidate if source tables in the task scope have cascade constraintsValidate if the timeout values are appropriate for a MySQL source or targetValidate max_statement_time database parameterValidate if Primary Key or Unique Index exist on target for Batch ApplyValidate if both Primary Key and Unique index exist on target for Batch ApplyValidate if secondary indexes are enabled during full load on the target databaseValidate if table has primary key or unique index when DMS validation is enabledRecommendation on using MaxFullLoadSubTasks settingCheck Transformation Rule for Digits RandomizeCheck Transformation Rule for Digits maskCheck Transformation Rule for Hashing maskVerify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneouslyVerify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneouslyCheck if source Amazon Aurora MySQL instance is not a read replicaCheck if binary log retention time is set properlyCheck if source tables do not have invisible columns.Validate if the database binlog format is set to ROW to support DMS CDCValidate that at least one selected object exists in the source databaseValidate that tables with generated columns exist in the source databaseValidate that skipTableSuspensionForPartitionDdl is enabled for partitioned tablesValidate that max_allowed_packet size can handle source LOB columnsValidate that secondary constraints and indexes (non-primary) are present in the source databaseValidate that row size of net changes table does not exceed 65535 when batch apply is enabledValidate that the target endpoint is not a read replicaValidate that number of tables to be migrated does not exceed 10,000Validate that binary logging is enabledValidate that AWS DMS is connected to a MySQL primary instance @@ -90,0 +91,10 @@ This section describes individual premigration assessments for migration tasks t + * Validate that row size of net changes table does not exceed 65535 when batch apply is enabled + + * Validate that the target endpoint is not a read replica + + * Validate that number of tables to be migrated does not exceed 10,000 + + * Validate that binary logging is enabled + + * Validate that AWS DMS is connected to a MySQL primary instance + @@ -401,0 +412,34 @@ This premigration assessment verifies that secondary constraints and indexes (fo +## Validate that row size of net changes table does not exceed 65535 when batch apply is enabled + +**API key** : `all-check-for-batch-apply-to-mysql` + +This premigration assessment checks if any table contains rows exceeding 65,535 bytes in size. When batch apply is enabled, AWS DMS cannot create temporary tables for rows exceeding this size due to MySQL engine limitations. + +## Validate that the target endpoint is not a read replica + +**API key** : `all-check-target-read-replica` + +This premigration assessment verifies that the target endpoint is not configured as a read replica. AWS DMS requires write access to the target database and cannot replicate to read-only replicas. + +## Validate that number of tables to be migrated does not exceed 10,000 + +**API key** : `mysql-check-10k-tables` + +This premigration assessment validates whether the number of tables to migrate exceeds 10,000 based on your table selection. + +## Validate that binary logging is enabled + +**API key** : `mysql-check-binlog-enabled` + +This premigration assessment validates whether binary logging is enabled on the source database. + +For more information, see [Using a self-managed MySQL-compatible database as a source for AWS DMS](./CHAP_Source.MySQL.html#CHAP_Source.MySQL.CustomerManaged). + +## Validate that AWS DMS is connected to a MySQL primary instance + +**API key** : `mysql-check-source-replica` + +This premigration assessment validates that the AWS DMS task source endpoint is a primary instance. + +For more information, see [Using a self-managed MySQL-compatible database as a source for AWS DMS](./CHAP_Source.MySQL.html#CHAP_Source.MySQL.CustomerManaged). +