Migrating databases to their Amazon RDS equivalents with AWS DMS
Homogeneous data migrations in AWS Database Migration Service (AWS DMS) simplify the migration of self-managed, on-premises databases to their Amazon Relational Database Service (Amazon RDS) equivalents. For example, you can use homogeneous data migrations to migrate an on-premises PostgreSQL database to Amazon RDS for PostgreSQL or Aurora PostgreSQL. For homogeneous data migrations, AWS DMS uses native database tools to provide easy and performant like-to-like migrations.
Homogeneous data migrations are serverless, which means that AWS DMS automatically scales the resources that are required for your migration. With homogeneous data migrations, you can migrate data, table partitions, data types, and secondary objects such as functions, stored procedures, and so on.
At a high level, homogeneous data migrations operate with instance profiles, data providers, and migration projects. When you create a migration project with the compatible source and target data providers of the same type, AWS DMS deploys a serverless environment where your data migration runs. Next, AWS DMS connects to the source data provider, reads the source data, dumps the files on the disk, and restores the data using native database tools. For more information about instance profiles, data providers, and migration projects, see Working with data providers, instance profiles, and migration projects in AWS DMS.
For the list of supported source databases, see Sources for DMS homogeneous data migrations.
For the list of supported target databases, see Targets for DMS homogeneous data migrations.
The following diagram illustrates how homogeneous data migrations work.
The following sections provide information about using homogeneous data migrations.
Topics
- Supported AWS Regions
- Features
- Limitations for homogeneous data migrations
- Overview of the homogeneous data migration process in AWS DMS
- Setting up homogeneous data migrations in AWS DMS
- Creating source data providers for homogeneous data migrations in AWS DMS
- Creating target data providers for homogeneous data migrations in AWS DMS
- Running homogeneous data migrations in AWS DMS
- Troubleshooting for homogeneous data migrations in AWS DMS
Supported AWS Regions
You can run homogeneous data migrations in the following AWS Regions.
| Region Name | Region |
|---|---|
| US East (N. Virginia) | us-east-1 |
| US East (Ohio) | us-east-2 |
| US West (Oregon) | us-west-2 |
| Asia Pacific (Tokyo) | ap-northeast-1 |
| Asia Pacific (Singapore) | ap-southeast-1 |
| Asia Pacific (Sydney) | ap-southeast-2 |
| Europe (Frankfurt) | eu-central-1 |
| Europe (Stockholm) | eu-north-1 |
| Europe (Ireland) | eu-west-1 |
Features
Homogeneous data migrations provide the following features:
-
AWS DMS automatically manages the compute and storage resources in the AWS Cloud that are required for homogeneous data migrations. AWS DMS deploys these resources in a serverless environment when you start a data migration.
-
AWS DMS uses native database tools to initiate a fully-automated migration between the databases of the same type.
-
You can use homogeneous data migrations to migrate your data as well as the secondary objects such as partitions, functions, stored procedures, and so on.
-
You can run homogeneous data migrations in the following three migration modes: full load, ongoing replication, and full load with ongoing replication.
-
For homogeneous data migrations, you can use on-premises, Amazon EC2, Amazon RDS databases as a source. You can choose Amazon RDS or Amazon Aurora as a migration target for homogeneous data migrations.
Limitations for homogeneous data migrations
The following limitations apply when you use homogeneous data migrations:
-
Homogeneous data migrations only support selection rules for MongoDB and Amazon DocumentDB migrations. DMS doesn't support selection rules for other database engines. Also, you can’t use transformation rules to change the data type of columns, move objects from one schema to another, or change the names of objects.
-
Homogeneous data migrations don't provide a built-in tool for data validation.
-
When using homogeneous data migrations with PostgreSQL, AWS DMS migrates views as tables to your target database.
-
Homogeneous data migrations don't capture schema-level changes during an ongoing data replication. If you create a new table in your source database, then AWS DMS can't migrate this table. To migrate this new table, restart your data migration.
-
You can't use homogeneous data migrations in AWS DMS to migrate data from a higher database version to a lower database version.
-
You can't use homogeneous data migrations in the CLI or API.
-
Homogeneous data migrations don't support establishing a connection with database instances in VPC secondary CIDR ranges.
-
You can't use the 8081 port for homogeneous migrations from your data providers.
