Amazon Aurora is a MySQL-compatible database engine that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. Migrating to Amazon Aurora from other database engine can help boost performance, reliability and availability of your databases while substantially reducing the total cost of ownership (TCO).
This webinar will introduce you to Amazon Aurora and focus on different options available for migration from your existing commercial and open source databases to Amazon Aurora. We will walk you through the entire process of migrating your existing databases to Amazon Aurora using AWS Database Migration Service
Learning Objectives:
• Learn about Amazon Aurora
• How Amazon Aurora performance, reliability availability compare to open source and commercial databases
• Key aspects of database migration
• Options available to migrate MySQL Databases from on-premises, EC2 and RDS to Amazon Aurora
• How to migrate Open Source and Commercial databases to Amazon Aurora using AWS Database Migration Service
3. Aurora is MySQL compatible
Fully compatible with MySQL 5.6
using the InnoDB storage engine
Code, applications, drivers, and
tools you already use with your
MySQL databases can be used
with Aurora with little or no change
4. Enterprise-class performance
Provides ~ 5X the throughput of standard
MySQL running on the same hardware.
Achieve up to 585,000 reads and 100,000
writes per second
Read replicas with <10ms latency
5. Highly available and durable
Six copies of data across three
Availability Zones with backups to
Amazon S3
Automated failover in less than 30
seconds
Instant crash recovery and survivable
caches
6. Highly scalable
Push button scaling from 2 vCPU
and 15GiB memory up to 32 vCPUs
and 244GiB memory
Automatic storage growth from 10G
to 64TB without performance impact
Scale reads with up to 15 low
latency read replicas
7. Multiple levels of security
Encrypt data at rest using keys you
create and control through AWS
KMS
Encrypt data in transit using SSL
Seamless encryption and
decryption, no application changes.
Complete network isolation using
Amazon VPC
8. Fully managed
Start database cluster in minutes
Automatic OS and database patching
Automatic backups and restores
In-built advanced monitoring and alerts
9. Low cost
Priced at 1/10th of the cost of
commercial database engines
No licenses, no lock-in, pay only for
what you use
Read replicas as standby instances
Up to 63% discounts with reserved
instances
12. Migration Factors: Source Database
Other MySQL
engines
Homogenous Migrations
Other non-
MySQL engines
Heterogenous Migrations
13. Migration Factors: Application Downtime
Migration with downtime Near zero downtime migration
binlog
replication
Replication
Instance
Load Backup
LoadBackup
14. Ease of migration
Migration cost
Schema migration complexity
Failback options
Migration of databases with multiple
shards
Migration of large databases
Other Migration Factors
16. DB Snapshot Migration
One-click migration from
RDS MySQL 5.6 to Aurora
Automatic conversion from
MyISAM to InnoDB
Migrate either manual or
automated snapshots
Most migrations finish
under one hour, can take
more time for very large
databases
DB
Snapshot
One-click
Migrate
RDS MySQL
Master/Slave New Aurora
Cluster
18. DB Snapshot Migration
Pros
Simplest method with the fewest number of steps
Will migrate over all schema objects, secondary indexes, and stored
procedures along with all of the database data
Cons
Requires downtime while snapshot is being migrated (or source DB must be in
read-only mode)
Currently only works with RDS MySQL 5.6 snapshots
Recommendation
Test migration time using previous RDS MySQL snapshot
Use DB snapshot migration if migration time within downtime requirements
19. Schema Migration Tools
Homogenous Schema Copy
Using mysqldump
AWS Database Migration Service (DMS) basic schema copy
Heterogenous Schema Migrations
AWS Schema Conversion Tool (migrate from Oracle, SQL Server, PostgreSQL)
Manual schema migration
Schema migration using other 3rd party tools
20. Migrate from Oracle, SQL Server and
PostgreSQL
Move your tables, views, stored
procedures, and data manipulation
language (DML) to MySQL, MariaDB,
PostgreSQL and Amazon Aurora
Know exactly where manual edits are
needed
Available for Microsoft Windows, Mac
and Linux desktops
AWS Schema Conversion
Tool
23. AWS Schema conversion tool
Pros
Automatic schema migration of most of your schema
Detailed database migration assessment report
Manual tasks categorized as simple (less than 1hr), medium (1 to 4 hrs)
and significant (more than 4 hrs)
No additional cost
Cons
Supports Oracle, SQL Server and PostgreSQL sources only
Recommendation
Create assessment report during migration planning
Use AWS Schema conversion tool for heterogeneous migrations
24. Data Movement Tools
Homogenous
• Using mysqldump / select into outfile
• AWS Database Migration Service one time copy
• AWS Database Migration Service with replication
• mysqldump + binlog replication
Heterogenous
AWS Database Migration Service one time copy
AWS Database Migration Service with replication
Data replication using other 3rd party tools
25. Move data to the same or different database
engine
Keep your apps running during the migration
Start your first migration in 10 minutes or less
Replicate within, to or from AWS EC2 or RDS
AWS Database Migration
Service
26. Customer
premises
Application users
AWS
Internet
VPN
Start a replication instance
Connect to source and target databases
Select tables, schemas, or databases
Let AWS Database Migration Service
create tables, load data, and keep
them in sync
Switch applications over to the target
at your convenience
DMS Migration Process
AWS
Database Migration
Service
28. AWS Database Migration Tool
Pros
Fast and parallel table loads
Migration can be paused and restarted
Selective table migration
Fully managed replication using agent-less change data capture (CDC)
Consolidate multiple sources in single target
No additional cost, pay only for replication instance and storage
Cons
Supports Oracle, SQL Server, PostgreSQL & MySQL compatible sources only
Recommendation
Use DMS for both homogenous and heterogeneous migrations, easy to get started
Use DMS if RDS DB snapshot migration takes long time
29. Aurora Database Migration Matrix
Source Database Type Migration With Downtime Near-zero Downtime Migration
RDS MySQL
Option 1: RDS Snapshot Migration
(Recommended)
Option 2: Database Migration Service
Option 3: Manual migration using mysqldump
Option 1: Schema migration with mysqldump +
Database Migration Service (Recommended)
Option 2: Manual migration using mysqldump and bin
log replication.
MySQL EC2/On-Prem
Option 1: Schema migration with mysqldump +
Database Migration Service (Recommended)
Option 2: Manual migration using mysqldump
Option 1: Schema migration with mysqldump +
Database Migration Service (Recommended)
Option 2: Manual migration using mysqldump and bin
log replication.
Oracle/SQL Server
Option 1: AWS Schema Conversion Tool +
Database Migration Service (Recommended)
Option 2: Manual/3rd party tool for schema
conversion and data movement
Option 1: AWS Schema Conversion Tool +
Database Migration Service (Recommended)
Option 2: Manual/3rd party tool for schema conversion
and data movement + 3rd party tool for replication
Other Non-MySQL Databases
Option: Manual/3rd party tool for schema
conversion and data movement
Option: Manual/3rd party tool for schema conversion
and data movement + 3rd party tool for replication