AWS dms documentation change
Summary
Added new validation checks for Data Validation/Masking compatibility, binary log retention time, and invisible columns in MariaDB migration assessments
Security assessment
The changes add documentation about proper configuration of Data Masking features (security controls) and warn against incompatible combinations with Data Validation. While these relate to security feature usage, there's no evidence of addressing an active vulnerability. The invisible columns check prevents data loss but isn't explicitly security-focused.
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md b/dms/latest/userguide/CHAP_Tasks.AssessmentReport.MariaDB.md index 7b7c0ccf8..80d9a0be5 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 mask +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 @@ -72,0 +73,10 @@ To create an individual premigration assessment using the AWS DMS API, use the l + * Verify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneously + + * Verify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneously + + * Verify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneously + + * Check if binary log retention time is set properly + + * Check if source tables do not have invisible columns + @@ -333,0 +344,30 @@ This assessment validates whether any of the columns used in the table mapping a +## Verify that Data Validation task settings and Data Masking Digit randomization are not enabled simultaneously + +**API key** : `all-to-all-validation-with-datamasking-digits-randomize` + +This premigration assessment verifies that Data Validation setting and Data Masking Digit randomization are not simultaneously enabled, as these features are incompatible. + +## Verify that Data Validation task settings and Data Masking Hashing mask are not enabled simultaneously + +**API key** : `all-to-all-validation-with-datamasking-hash-mask` + +This premigration assessment verifies that Data Validation setting and Data Masking Hashing mask are not simultaneously enabled, as these features are incompatible. + +## Verify that Data Validation task settings and Data Masking Digit mask are not enabled simultaneously + +**API key** : `all-to-all-validation-with-digit-mask` + +This premigration assessment verifies that Data Validation setting and Data Masking Digit mask are not simultaneously enabled, as these features are incompatible. + +## Check if binary log retention time is set properly + +**API key** : `mariadb-check-binlog-retention-time` + +This premigration assessment validates whether the value of '`binlog retention hours`' is larger than 24 hours. + +## Check if source tables do not have invisible columns + +**API key** : `mariadb-check-invisible-columns` + +This premigration assessment validates whether source tables do not have invisible columns. AWS DMS does not migrate data from invisible columns in your source database. +