"Exploring AWS DMS: Versatile Migration for Seamless Transitions"🚠

Amazon Web Services (AWS) Database Migration Service (DMS) is a robust and fully-managed solution designed to facilitate seamless and secure migration of databases to the AWS cloud environment. This service caters to a broad spectrum of migration scenarios, accommodating both homogeneous migrations, where the source and target databases share the same engine (e.g., Oracle to Oracle), and heterogeneous migrations, where the source and target databases differ (e.g., Oracle to Amazon Aurora or Microsoft SQL Server to Amazon Redshift).

DMS Sources and Targets🛳️

SOURCES:

• On-premises and EC2 instances databases: Oracle, Ms SQL Server, MySQL, MariaDB, PostgreSQL, MongoDB, SAP, DB2

• Azure: Azure SQL Database

• Amazon RDS: all including Aurora

• Amazon S3

• DocumentDB

TARGETS:

• On-premises and EC2 instances databases: Oracle, MS SQL Server, MySQL, MariaDB, PostgreSQL, MongoDB, SAP

• Amazon RDS including Aurora

• Amazon DynamoDB

• Amazon S3

• OpenSearch Service

• Kinesis Data Streams

• DocumentDB

AWS Schema Conversion Tool (SCT):🏑

The AWS Schema Conversion Tool (AWS SCT) is a software application provided by Amazon Web Services (AWS) to facilitate the migration of database schemas from one database engine to another. It helps in converting database schema structures, including tables, views, stored procedures, and other database objects, between different database engines. This tool is particularly useful when migrating databases from on-premises environments or other cloud providers to AWS.

• Example OLTP: ( SQL Server or Oracle) to MYSQL, PostgreSQL, Aurora

• Example OLAP: ( Teradata or Oracle) to Amazon Redshift

• You do not need to use SCT if you are migrating the same DB engine

  • Ex: On-Premise PostgreSQL => RDS PostgreSQL

  • The DB engine is still PostgreSQL ( RDS is the platform)

DMS -Good thing to know

• Work over VPC Peering, VPN ( site to site, software), Direct Connect

• Supports Full Load, Full Load + CDC, or CDC only

• Oracle :

  • Source: Supports TDE for the source using "BinaryReader"

  • Target: Supports BLOBs in table that have a primary key, and TDE

• OpenSearch :

  • Source: does not exist

  • Target: possible to migrate from a relational database using DMS

  • Therefore, DMS cannot be used to replicate OpenSearch data

Snowball Integration with AWS Database Migration Service (DMS):

• Larger data migrations can include many terabytes of information

• Can be limited due to network bandwidth or size of data

• AWS DMS can use Snowball Edge & Amazon S3 to speed up

  migration

An overview if how its works:

you use the AWS Schema Conversion Tool(AWS SCT) to extract the data locally and move it to an Edge device. You ship the Edge device or devices back to AWS. After AWS receives your shipment, the Edge device automatically loads its data into an Amazon S3 bucker. AWS DMS takes the files and migrates the data to the target data store. If you are using change data capture(CDC), those updates are written to the Amazon S3 bucket and then applied to the target data store.🏬

To sum it up, using the AWS Schema Conversion Tool is a wise choice to make the transition more efficient and less complicated as it handles the nitty-gritty details of adjusting database structures and code for a new system. I have offered you a glimpse into the concept. Keep in mind that as you explore the realm of database migration, the AWS Schema Conversion Tool serves as your guide, simplifying complexities and ensuring a clear path of your data journey.🏇🏿