AWS dms documentation change
Summary
Added five new premigration assessment checks for MariaDB migrations: validating row size doesn't exceed 65535 bytes when batch apply is enabled, target endpoint is not a read replica, number of tables doesn't exceed 10,000, binary log is enabled, and views from selection rules exist on source.
Security assessment
The changes add routine validation checks for migration configuration and compatibility. While some checks (like binary log enablement) relate to replication functionality, there is no evidence these changes address a specific security vulnerability, weakness, or incident. The changes are standard documentation updates for premigration assessment features.
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md b/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md index 084e84be1..3af7821dc 100644 --- a//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md +++ b//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md @@ -7 +7 @@ -Validate if the server_id is set to 1 or greater in the source databaseValidate 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 Binary Log transaction compression is disabledValidate if DMS user has REPLICATION CLIENT and REPLICATION SLAVE privileges for the source databaseValidate if DMS user has SELECT permissions for the source database tablesValidate if DMS user has necessary privileges for the MySQL-compatible database as a targetValidate 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 format is set to ROW to support DMS CDCValidate if the database binlog image is set to FULL to support DMS CDCValidate if the source database is a MariaDB Read-ReplicaValidate if a table has partitions, and recommend TRUNCATE_BEFORE_LOAD or DO_NOTHING 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 source tables in the task scope have generated columnsValidate if the timeout values are appropriate for a MariaDB sourceValidate if the timeout values are appropriate for a MariaDB 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 binary log retention time is set properlyCheck if source tables do not have invisible columnsValidate that at least one selected object exists in the source databaseValidate that skipTableSuspensionForPartitionDdl is enabled for partitioned tablesValidate that secondary constraints and indexes (non-primary) are present in the source database +Validate if the server_id is set to 1 or greater in the source databaseValidate 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 Binary Log transaction compression is disabledValidate if DMS user has REPLICATION CLIENT and REPLICATION SLAVE privileges for the source databaseValidate if DMS user has SELECT permissions for the source database tablesValidate if DMS user has necessary privileges for the MySQL-compatible database as a targetValidate 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 format is set to ROW to support DMS CDCValidate if the database binlog image is set to FULL to support DMS CDCValidate if the source database is a MariaDB Read-ReplicaValidate if a table has partitions, and recommend TRUNCATE_BEFORE_LOAD or DO_NOTHING 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 source tables in the task scope have generated columnsValidate if the timeout values are appropriate for a MariaDB sourceValidate if the timeout values are appropriate for a MariaDB 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 binary log retention time is set properlyCheck if source tables do not have invisible columnsValidate that at least one selected object exists in the source databaseValidate that skipTableSuspensionForPartitionDdl is enabled for partitioned tablesValidate 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 target endpoint is not a read replicaValidate that number of tables to be migrated doesn't exceed 10,000Validate that binary log is enabledCheck that views from selection rules exist on source @@ -90,0 +91,10 @@ To create an individual premigration assessment using the AWS DMS API, use the l + * Validate that row size of net changes table does not exceed 65535 when batch apply is enabled + + * Validate that target endpoint is not a read replica + + * Validate that number of tables to be migrated doesn't exceed 10,000 + + * Validate that binary log is enabled + + * Check that views from selection rules exist on source + @@ -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` + +The 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 engine limitations. + +## Validate that 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 doesn't exceed 10,000 + +**API key** : `mariadb-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 log is enabled + +**API key** : `mariadb-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). + +## Check that views from selection rules exist on source + +**API key** : `mariadb-check-views` + +This premigration assessment validates whether views are used, as AWS DMS does not support views migration for MariaDB. + +For more information, see [Limitations on using a MySQL database as a source for AWS DMS](./CHAP_Source.MySQL.html#CHAP_Source.MySQL.Limitations). +