AWS AmazonRDS documentation change
Summary
Updated migration documentation to expand supported sources beyond EC2 to include on-premises and other cloud providers. Added network setup requirements, clarified downtime implications, restructured prerequisites with links to DMS documentation, and updated limitations.
Security assessment
The changes primarily broaden migration source types and improve documentation clarity. No security vulnerabilities or weaknesses are addressed. The added note about PostgreSQL's idle_in_transaction_session_timeout relates to operational reliability, not security.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/USER_DMS_migration.md b/AmazonRDS/latest/AuroraUserGuide/USER_DMS_migration.md index 32c3c8c4c..76dc622e2 100644 --- a//AmazonRDS/latest/AuroraUserGuide/USER_DMS_migration.md +++ b//AmazonRDS/latest/AuroraUserGuide/USER_DMS_migration.md @@ -9 +9 @@ OverviewPrerequisitesLimitations -# Auto migrating EC2 databases to Amazon Aurora using AWS Database Migration Service +# Auto migrating databases to Amazon Aurora using AWS Database Migration Service @@ -11 +11 @@ OverviewPrerequisitesLimitations -You can use the Aurora console to migrate an EC2 database to Aurora. Aurora uses AWS Database Migration Service (AWS DMS) to migrate your source EC2 database. AWS DMS allows you to migrate relational databases into your AWS Cloud. For more information about AWS Database Migration Service, see [What is AWS Database Migration Service?](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html) in the _AWS Database Migration Service User Guide_. +You can use the Aurora console to migrate a database from an EC2, on-prem or other cloud provider instance to Aurora. AWS Database Migration Service (AWS DMS) is used for this. For more information about it, see [What is AWS Database Migration Service?](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html) in the _AWS Database Migration Service User Guide_. @@ -13 +13 @@ You can use the Aurora console to migrate an EC2 database to Aurora. Aurora uses -To begin the migration, you must create an equivalent Aurora DB cluster to migrate the data into. After you create your target database, you can import your EC2 database into it. For source databases smaller than 1TiB, this migration action reduces the time and resources required to migrate your data into Aurora . +To begin the migration, you must create an equivalent Aurora DB cluster. After you create your target database, you can import your source into it. For source databases smaller than 1TiB, this migration action reduces the time and resources required to migrate your data into Aurora . @@ -17 +17 @@ To begin the migration, you must create an equivalent Aurora DB cluster to migra -The Aurora console allows you to migrate EC2 databases into equivalent Aurora databases. You must create an Aurora database to enable migration from the console. +The Aurora console allows you to migrate EC2, on-prem or other cloud provider database into equivalent Aurora database. You must create an Aurora database to enable migration from the console. @@ -19 +19,5 @@ The Aurora console allows you to migrate EC2 databases into equivalent Aurora da -You can migrate EC2 databases for the following databases engines: +###### Note + +For the databases to be equivalent, they must have the same database engine and compatible engine versions. + +This approach can be used for the following database engines: @@ -30 +34 @@ The migration process involves the following steps: - * Create an equivalent database in Aurora. For the databases to be equivalent, they must have the same database engine and compatible engine versions. They must also be in the same VPC. For instructions on creating your database, see [Creating an Amazon Aurora DB cluster](./Aurora.CreateInstance.html) . + * Create an equivalent database in Aurora. Then, set up a proper network between source and target. For EC2 instances in the same region, account, and VPC, network setup can be skipped. For more information, see [Setting up a network](https://docs.aws.amazon.com/dms/latest/userguide/dm-network.html) in the _AWS Database Migration Service User Guide_. For instructions on creating your database, see [Creating an Amazon Aurora DB cluster](./Aurora.CreateInstance.html). @@ -38 +42 @@ The migration process involves the following steps: -This option causes an outage in your Aurora database. +This option requires downtime. Your target Aurora database will be unavailable to applications during the migration process. @@ -44 +48 @@ This option causes an outage in your Aurora database. -This option causes an outage in your Aurora database. +This option requires downtime. Your target Aurora database will be unavailable to applications during the migration process. @@ -48 +52 @@ This option causes an outage in your Aurora database. - * Aurora creates the necessary networking resources to facilitate the migration. Once Aurora creates the required resources, it notifies you about the resources created and allows you to initiate the data transfer. + * Aurora creates the necessary resources to facilitate the migration. Once Aurora creates the required resources, it notifies you about the resources created and allows you to initiate the data transfer. @@ -57,3 +61 @@ The time required to complete the migration depends on the type of replication a -### MySQL - -Before you begin to work with a MySQL database as the source database, make sure that you have the following prerequisites. These prerequisites apply to AWS-managed sources. + * [Setting up a network](https://docs.aws.amazon.com/dms/latest/userguide/dm-network.html) (for EC2s in the same region, account and VPC, it can be skipped) @@ -61 +63 @@ Before you begin to work with a MySQL database as the source database, make sure -You must have an account for AWS DMS that has the Replication Admin role. The role needs the following privileges: + * Setting up source and target databases @@ -63 +65 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro - * **REPLICATION CLIENT** – This privilege is required for CDC tasks only. In other words, full-load-only tasks don't require this privilege. + * **MySQL** @@ -65 +67 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro - * **REPLICATION SLAVE** – This privilege is required for CDC tasks only. In other words, full-load-only tasks don't require this privilege. +Please follow the following basic prerequisites for your source database: @@ -66,0 +69 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro + * [Using MySQL as a source](https://docs.aws.amazon.com/dms/latest/userguide/dm-data-providers-source-mysql.html) @@ -67,0 +71 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro +Please follow the following basic prerequisites for your target database: @@ -68,0 +73 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro + * [Using MySQL as a target](https://docs.aws.amazon.com/dms/latest/userguide/dm-data-providers-target-mysql.html) @@ -70 +75 @@ You must have an account for AWS DMS that has the Replication Admin role. The ro -The AWS DMS user must also have SELECT privileges for the source tables designated for replication. +Additionally when migrating from a MySQL source database, your Aurora account must have the Replication Admin role. You must also have the proper privileges applied for that role. @@ -72 +77 @@ The AWS DMS user must also have SELECT privileges for the source tables designat -Grant the following privileges if you use MySQL-specific premigration assessments. + * **PostgreSQL** @@ -73,0 +79 @@ Grant the following privileges if you use MySQL-specific premigration assessment +Please follow the following prerequisites for your source database: @@ -75,4 +81 @@ Grant the following privileges if you use MySQL-specific premigration assessment - grant select on mysql.user to <dms_user>; - grant select on mysql.db to <dms_user>; - grant select on mysql.tables_priv to <dms_user>; - grant select on mysql.role_edges to <dms_user> #only for MySQL version 8.0.11 and higher + * [Using PostgreSQL as a source](https://docs.aws.amazon.com/dms/latest/userguide/dm-data-providers-source-postgresql.html) @@ -80 +83 @@ Grant the following privileges if you use MySQL-specific premigration assessment -### PostgreSQL +Please follow the following prerequisites for your target database: @@ -82 +85 @@ Grant the following privileges if you use MySQL-specific premigration assessment -Before migrating data from an AWS-managed PostgreSQL source database, do the following: + * [Using PostgreSQL as a target](https://docs.aws.amazon.com/dms/latest/userguide/dm-data-providers-target-postgresql.html) @@ -84 +87 @@ Before migrating data from an AWS-managed PostgreSQL source database, do the fol - * We recommend that you use an AWS user account with the minimum required permissions for the PostgreSQL DB instance as the user account for the PostgreSQL source endpoint for AWS DMS. Using the master account is not recommended. The account must have the `rds_superuser` role and the `rds_replication` role. The `rds_replication` role grants permissions to manage logical slots and to stream data using logical slots. +###### Note @@ -85,0 +89 @@ Before migrating data from an AWS-managed PostgreSQL source database, do the fol +Some AWS DMS transactions are idle for some time before the DMS engine uses them again. By using the parameter `idle_in_transaction_session_timeout` in PostgreSQL versions 9.6 and higher, you can cause idle transactions to time out and fail. @@ -89,3 +92,0 @@ Before migrating data from an AWS-managed PostgreSQL source database, do the fol -###### Note - -Some AWS DMS transactions are idle for some time before the DMS engine uses them again. By using the parameter `idle_in_transaction_session_timeout` in PostgreSQL versions 9.6 and higher, you can cause idle transactions to time out and fail. @@ -99,3 +100 @@ The following limitations apply to the auto-migrate process: - * When migrating from a MySQL source database, your Aurora account must have the Replication Admin role. You must also have the proper privileges applied for that role. - - * Your EC2 instance and target database must be in the same VPC. + * You can migrate your source database only to a database: @@ -103 +102 @@ The following limitations apply to the auto-migrate process: - * You can't migrate your EC2 database to the following target databases when using the **Migrate data from EC2 database** action: + * that is not any of the following: @@ -111 +110 @@ The following limitations apply to the auto-migrate process: - * Databases with MySQL version lower than 5.7 + * that uses a supported version of MySQL or PostgreSQL as listed [here](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.Sources.html#CHAP_Introduction.Sources.HomogeneousDataMigrations) @@ -113 +112 @@ The following limitations apply to the auto-migrate process: - * Databases with PostgreSQL version lower than 10.4 + * [Limitations of DMS](https://docs.aws.amazon.com/dms/latest/userguide/data-migrations.html#data-migrations-limitations) @@ -117,0 +117,4 @@ The following limitations apply to the auto-migrate process: +###### Note + +Although underlying AWS DMS tool supports selection rules for certain migration scenarios, the auto-migrating databases to Aurora feature does not. +