nSights Talks

Introduction to AWS Database Migration Service

Tutorial Highlights & Transcript

00:00 - Beginning of Video
Hello everyone. Myself, I’m Mohammed Raiyan. I have been working as a support engineer in nClouds for the last six months. Today, I’m going to do a short demo on the Introduction to AWS Database Migration Service.
00:24 - What is AWS Database Migration Service (AWS DMS)?
AWS DMS is nothing but a concept of all customers or an existing customer to migrate data from one source of engine to another source.

For example, if a customer was willing to migrate into cloud computing, AWS Database Migration Service works here to migrate the whole data into the cloud computing. This should be from on-premise to cloud computing or from the same search engine in the cloud CPU or migrating from one set of database engines to another set database engine.

AWS is a web service that you can use to migrate from a source data store to a target data store. Those two stores are called endpoints. You can migrate between source and target endpoint that use the same database engine such as Oracle database to another Oracle database. You can also migrate between the two sets of different engines like Oracle database to a PostgreSQL database. The only requirement that AWS DMS needs is that one of your endpoints must be in AWS, and you can’t use AWS Database Migration Service for an on-premise database to another on-premise database.

01:45 - The AWS DMS process
Process involves three main characters and one is AWS DMS. The application server here helps as a bridge which helps you to migrate data from one data to another data. Those two endpoints will be your source data and the target database endpoints and the task of configuring your cue for your DMS for the replication instance. The task name can be a unique identifier that makes you easily identify your task.
03:36 - Step-by-step demo tutorial
Moving quick to the demo, I have a test sample here. I’m going to use both of those my source endpoint and target endpoint within the AWS. I have already created two databases here. This is AWS DMS. First, let’s start with the replication instance. Create a replication instance. Name as demo and go to description.

It’s optional. We can directly come here to our preferred search engine. I am here at preferred for a demo today and your engine version, then your VPC. If you had a separate VPC here, you can use that or you can go with the default VPC.

Multi AZ is just more of its similar availability within the database and your migration. It’s more of a single AZ where the Multiple AZ costs are double of the cost for a replica instance. Once this is created, simply go with create.

I have already created one so I’ll just go with this. Endpoint, let’s set our source and target endpoints here, for source I’ll be using here as the RDS DB instance. My Source will be Maria database. It will automatically get your database and your search engine line. If you had configured your database with AWS Secrets Manager it would work only within the AWS data, or else if you had an on-premise server, which is outside of the AWS network, you can provide your details here from server name, port name, user, and admin in this thing.

Let me give my password Source Endpoint had created. Let’s create our Target Endpoint. The Target will also be in RDS. My Target is not the same database engine. It’s a MySQL database engine. Same process follows here and I created it. This should be one from On-Premise server or your targets from the On-Premise server, or both should be in different database engines, as well. This works smoothly with AWS DMS. The condition as I said earlier is one of the sources or one of the targets should be in your AWS.

Next, we will create a database migration task here. This task is configured to do the whole process of what is not included. We will name it test demo. My replica I selected which I had created my Source Endpoint would be my Maria database and my target would be MySQL database, so migration type does provide three types. One is migrating the existing data, which is a one-time task which runs on complete as it is. The next one will be migrating the existing data and also replicating ongoing changes.

If the client wants to go with the On-Premise as well as the migration with AWS cloud, this is preferable and the client also wants to have the whole database structure as it is and also looking forward to integrating with the new data structure. This option works better. If you’re looking for new changes, which only need to be migrated to a database, then we’ll go for replicate data changes.

As an example I’ve just created here, so task setting gives your Wizard or if you prefer with the JSON editor you can also go with that, Target data preparation just go with do nothing. The large object mode will be full LOB mode for large data; it totally depends on the database.

One of the rules should be added here. If you don’t have schema here, if I had a schema name I’d just mention it here or you go wild card for the whole schema and the all database here. If you want to exclude something specific or include in your migration process, you can add it from here, exclude or include.

Once the migration task is created it will start processing your database so our migration task will be started from here. It will be using replica instances to connect the endpoints between one database to another database. Quickly for the demo I just created an instance and a task that might complete or might come with– in real-time it may differ with the work you serviced. It’s just a basic for how AWS DMS works here. My database is starting to progress.

This is how the AWS DMS works. This was very basic for understanding how the DMS works and how to set up the DMS, it totally depends on the database structure and their different types of data migration. This will be given updates to a new user to understand what AWS DMS is and how it works.

Back to our slide, so we have seen that once the progress is completed it will show the logs as well as the progression details if one or two errors are made. The AWS business technician– client should be more clear that every database if you’re migrating from a different database into another database, in which there might not be 100% compatible with the data migration. We should precaution them as I said earlier for a backup it’s better to go with your RDS backup, or On-Premise backup before taking a step in AWS DMS. This is so far for the basics of the introduction to AWS DMS.

Jasmeet Singh

Mohammed Raiyan

Support Engineer


Raiyan is a DevOps Support Engineer at nClouds. He is an experienced specialist with a demonstrated history of working with data migration, DevOps, and AWS cloud.