AWS Database Migration Service
Learn about the AWS DMS and walk through a detailed example.
The AWS DMS allows the migration of data from one database to another. It was initially launched in 2016 with the goal of allowing easy, secure, and cost-effective migrations with no downtime.
It’s possible to migrate within the same database engine (e.g., from an Oracle database to another Oracle database) or to migrate between different database engines (e.g., from an Oracle database to a MySQL database). When migrating to another database engine, the AWS Schema Conversion Tool (SCT) can assist in migrating the database schema and code.
In the context of ingesting databases into a data lake architecture, the AWS team considers Amazon S3 to be the basis of the data lake. However, S3 is just one of the data stores that AWS DMS supports.
Supported source and target databases
AWS DMS supports a variety of databases. However, either the source or the target database (or both) must be hosted on AWS (e.g., on Amazon RDS or EC2).
Supported Databases in AWS DMS
Source Databases | Target Databases |
|
|
|
|
AWS Schema Conversion Tool
Migrating from one SQL database engine to another can become more complex than expected due to the SQL variants or dialects that exist. For example, Microsoft, Oracle, and PostgreSQL have expanded upon standard SQL in their implementations of the Structured Query Language.
By itself, the AWS DMS doesn’t convert database schemas or the SQL code for views, stored procedures, and functions. The AWS SCT is a downloadable add-on tool designed to do the conversion for the database schema and code. If database objects can’t be converted automatically, the SCT tool marks them for manual review and conversion.
SCT has its own source and ...