I want to migrate my data from one DB engine to another using AWS Database Migration Service (AWS DMS).
Short description
You can use AWS DMS to migrate relational databases, data warehouses, NoSQL databases, and other types of data stores. You can use AWS DMS to migrate between on-premises instances or between combinations of cloud and on-premises setups.
AWS DMS supports both homogeneous (between two databases with the same engine) and heterogeneous (between different database engines) migrations. For example, a homogeneous migration could be from an Oracle database to an Oracle database and a heterogeneous migration could be from Oracle to MySQL.
When you use AWS DMS, either the source or target database must be on an AWS service. For example, you can use AWS DMS to migrate to AWS from an on-premises database, or from an AWS database service to an on-premises environment.
Resolution
AWS DMS creates only the minimum number of objects that are required to efficiently migrate the data. However, you can migrate most or all of the source schema.
If you perform a homogeneous migration, you can migrate the schema by using your engine's native tools to export and import only the schema. If your migration is heterogeneous, you can use the AWS Schema Conversion Tool (AWS SCT) to generate a complete target schema. For more information, see Getting started with AWS SCT.
If AWS DMS meets your source and target DB engine's needs, see Setting up for AWS Database Migration Service. Then, confirm that the AWS DMS replication instance can connect to both the source and target databases. For more information about common networking scenarios, see Security in AWS Database Migration Service.
When you're ready to migrate your data, see Getting Started with AWS Database Migration Service.
Related information
Troubleshooting migration tasks in AWS Database Migration Service
Database migration step-by-step walkthroughs
Migration strategy for relational databases