AWS dms documentation change
Summary
Added three new premigration assessment checks: 1) Validate that at least one selected object exists in the source database, 2) Validate that skipTableSuspensionForPartitionDdl is enabled for partitioned tables, 3) Validate that secondary constraints and indexes are present in the source database.
Security assessment
The changes add operational checks for migration configuration and data integrity, but contain no references to security vulnerabilities, access controls, encryption, or security incidents. The added validations focus on migration reliability (partitioned table handling), object selection verification, and index/constraint presence - all operational concerns without security implications.
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md b/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md index 80d9a0be5..b16dd57f1 100644 --- a//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md +++ b//dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md @@ -5 +5 @@ -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 columns +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 @@ -82,0 +83,6 @@ To create an individual premigration assessment using the AWS DMS API, use the l + * Validate that at least one selected object exists in the source database + + * Validate that skipTableSuspensionForPartitionDdl is enabled for partitioned tables + + * Validate that secondary constraints and indexes (non-primary) are present in the source database + @@ -373,0 +380,20 @@ This premigration assessment validates whether source tables do not have invisib +## Validate that at least one selected object exists in the source database + +**API key** : `all-check-source-selection-rules` + +This premigration assessment verifies that at least one object specified in the selection rules exists in the source database, including pattern matching for wildcard-based rules. + +## Validate that `skipTableSuspensionForPartitionDdl` is enabled for partitioned tables + +**API key** : `mariadb-check-skip-table-suspension-partition-ddl` + +This premigration assessment detects partitioned tables in the source database and verifies the `skipTableSuspensionForPartitionDdl` parameter setting. Failure to set this parameter may result in unnecessary table suspensions during migration. + +For more information, see [Limitations on using a MySQL database as a source for AWS DMS](./CHAP_Source.MySQL.html#CHAP_Source.MySQL.Limitations). + +## Validate that secondary constraints and indexes (non-primary) are present in the source database + +**API key** : `all-check-secondary-constraints` + +This premigration assessment verifies that secondary constraints and indexes (foreign keys, check constraints, non-clustered indexes) are present in the source database. +