This document discusses migrating on-premises databases to the AWS cloud using the AWS Database Migration Service (AWS DMS) and Amazon Redshift. AWS DMS can migrate data between most commercial and open-source databases to AWS services like Redshift and Aurora with minimal downtime. The document outlines considerations for database migration and provides examples of using AWS DMS and the AWS Schema Conversion Tool to migrate an Oracle database to a PostgreSQL database on Redshift.
2. Why Migrate Databases to the Cloud?
Development and
Operational Flexibility
Managed ServicePerformance and
Scalability
Fault Tolerance and
Availability
4. It can migrate your data to and from most widely
used commercial
AWS Database
Migration Service
(AWS DMS)
Amazon
Redshift
Amazon
Aurora
AWS DMS migrates databases to AWS easily and
securely with minimal downtime.
and open-source databases.
5. Customer
Premises
Application Users
AWS
Internet
VPN
Start a replication instance
Connect to source and target databases
Select tables, schemas or databases
Let the AWS Database Migration
Service create tables, load data and
keep them in sync
Switch applications over to the target
at your convenience
Applications Keep Running During Migration
AWS
DMS
6. When to Use the Database Migration Service
AWS DMS can act as a
replication/migration Swiss Army knife…
Use it for:
• Heterogeneous migrations
• Minimal downtime required
• No native solution
Apply caution when you have:
• Some tables with large binary objects
• Complex data types
• A high load database
7. When to Use the Database Migration Service
…but AWS DMS is not a magic wand.
Check the documentation on limitations you may
encounter with your source and target DBMS:
• For example, the AUTO_INCREMENT
attribute of MySQL sources will not be
replicated to a target
• Each source and target has its own set
of limitations
8. AWS SCT helps automate many database schema
and code conversion tasks when migrating between
database engines, or data warehouse engines.
AWS
Schema
Conversion Tool
Amazon
Redshift
Amazon
Aurora
Amazon
DynamoDB
10. OLTP Conversions Supported by AWS SCT
Source Database Target Database on Amazon RDS
Microsoft SQL Server (version 2008
and later)
Amazon Aurora (MySQL or PostgreSQL),
Microsoft SQL Server, MySQL, PostgreSQL
MySQL (version 5.6 and later) Amazon Aurora (PostgreSQL), MySQL,
PostgreSQL
Oracle (version 10.2 and later) Amazon Aurora (MySQL or PostgreSQL),
MySQL, PostgreSQL
PostgreSQL (version 9.1 and later) Amazon Aurora (MySQL), MySQL,
PostgreSQL
Note: schema and data can be migrated from MySQL to an Amazon Aurora
(MySQL) cluster without using the Schema Conversion Tool.
11. Recently Announced Enhancements
Released
SCT - Extract of Oracle DW and Teradata data Feb 17
DMS – Amazon S3 as a Target Mar 29
DMS – Amazon DynamoDB as a Target Apr 11
DMS – MongoDB as a Source Apr 11
SCT – Vertica & SQL Server conversion to Amazon Redshift Apr 19
SCT – Extract of Netezza, Greenplum & Vertica data Apr 19
SCT – Extract of SQL Server DW data May 12
DMS – Supported by AWS CloudFormation Jul 12
12. Database Migration is a Multi-phase Process
Phase Description Automation Effort
1 Assessment SCT 2%
2 Database Schema Conversion SCT and/or DMS 14%
3 Application Conversion & Remediation SCT 25%
4 Scripts Conversion SCT 7%
5 Integration with 3rd Party Applications 3%
6 Data Migration DMS 4%
7 Functional Testing of the Entire System 29%
8 Performance Tuning SCT 2%
9 Integration and Deployment 7%
10 Training and Knowledge 2%
11 Documentation and Version Control 2%
12 Post Production Support 3%