AWS dms documentation change
Summary
Added a note advising against using wildcards in database mapping rules to prevent migration of system databases
Security assessment
The note addresses operational best practices to avoid migration failures due to insufficient permissions on system databases. It does not directly relate to security vulnerabilities or introduce security features.
Diff
diff --git a/dms/latest/userguide/CHAP_Source.MySQL.md b/dms/latest/userguide/CHAP_Source.MySQL.md index 90103b13a..fc66bdea2 100644 --- a//dms/latest/userguide/CHAP_Source.MySQL.md +++ b//dms/latest/userguide/CHAP_Source.MySQL.md @@ -39,0 +40,4 @@ For additional details on working with MySQL-compatible databases and AWS DMS, s +###### Note + +When configuring AWS Database Migration Service (AWS DMS) mapping rules, it is important to avoid using wildcards (%) for database or schema names. Instead, you must explicitly specify only the user-created databases that need to be migrated. Using a wildcard character includes all databases in the migration process, including system databases which are not required on the target instance. Since the MySQL Amazon RDS master user lacks the necessary permissions to import data into target system databases, attempting to migrate these system databases fails. +