Cookies on this site

We would like to use cookies to understand how the site is used and to measure our campaigns. Nothing is set until you choose, and you can change your mind at any time from “Cookie settings” at the foot of every page. Privacy policy

Contact UsContact Us

Resources / Blogs

Cloud & apps

A beginner’s guide to getting started with AWS Database Migration Service (AWS DMS)

Before the option for AWS DMS solution for your company, it’s good to have a fair knowledge about the steps to get started with it. That’s what we are going to discuss in this blog with a simple approach.

· · 2 min read

A beginner’s guide to getting started with AWS Database Migration Service (AWS DMS)

AWS Database Migration Service (AWS DMS) is a cloud-based service that simplifies the migration of relational databases, data warehouses, NoSQL databases, and other data stores. AWS DMS can be used to migrate data into the AWS Cloud, between on-premises instances, or between cloud and on-premises configurations.

Before the option for AWS DMS solution for your company, it’s good to have a fair knowledge about the steps to get started with it. That’s what we are going to discuss in this blog with a simple approach.

3 main steps to get started with AWS DMS:

Sign into your AWS account

There are two distinct user kinds in AWS. Either you are an IAM user or the root user of the account. Depending on what kind of AWS user you are, a different procedure will be used to sign in to your account. When an AWS account is created with the same email address and password that were used to create the account, the root user is also created. Within the AWS account, either the root user or an IAM administrator can create IAM users.

Start a database migration

After signing into the AWS account, the next step is to start the database migration. AWS Database Migration Service offers both homogeneous migrations and heterogeneous migrations.

Homogeneous Migrations – When migrating a homogeneous database, just one step is required because the source and target database engines are the same or compatible. You set up a migration task with connections to the source and target databases, and with a click, you can begin the migration. The rest is handled by the AWS Database Migration Service.

Heterogeneous Migrations – In this migration type, the engines for the source and target databases are different. There is a two-step approach for heterogeneous migrations. First, change the source code and schema to match the target database using the AWS Schema Conversion Tool. After that, transfer data from the source database to the target database using the AWS Database Migration Service. During the migration, all necessary data types will be automatically converted.

Create a replication instance

This is the final step where we create a replication instance. The actual data transfer between the source and target endpoints is carried out by a replication instance. For the tasks that move data from your source database to your target database, your instance needs enough storage and processing power. The amount of data to transfer and the duties your instance must perform will determine how big this replication instance has to be.

Conclusion

Briefly said, you may easily and securely migrate databases from on-premises databases, DB instances, or databases running on AWS EC2 instances to the cloud using the AWS Database Migration Service (DMS).

However, the AWS DMS process might become challenging at multiple points in time. Contact the Princeton IT team of professionals for all of your AWS DMS requirements to leverage AWS DMS technology in a seamless way to achieve your business goals.

← All articles

Case studies

Cloud Consulting in practice

Client names are withheld. We are happy to share details on a call.

All case studies
  • Delivered

    On-prem → Amazon RDS

    Nonprofit

    Cloud Consulting

    Oracle from on-premises to Amazon RDS for a national nonprofit

    The nonprofit's on-premises Oracle database had become hard to maintain and scale. We planned the move with automated workflows and validation tests, migrated to Amazon RDS for Oracle with minimal disruption and left a repeatable process for future changes.

    • Automated, tested migration
    • Less day-to-day database upkeep
  • Delivered

    600k files, < 3 days

    Document management

    Microsoft

    600,000 documents moved from ImageRight to SharePoint in under three days

    A one-file-at-a-time script would have needed about 22 days of continuous running. We rebuilt the migration around a SQL work queue with parallel uploads, automatic retries and crash recovery, and it finished unattended in under three days.

    • 1,125 → 8,314 files per hour
    • Under 3 days instead of about 22
  • Delivered

    Every change, flagged

    Food manufacturing

    AI Consulting

    Label comparison agent for a national food cooperative

    Compares two versions of a product label, highlights every change, annotates the PDF and returns an audit-ready list of differences. We moved it from Copilot Studio to Azure Functions when the document processing outgrew the low-code platform.

    • Audit-ready differences in one chat turn
    • Rebuilt from low-code to cloud functions

Keep reading

All Cloud & apps articles

Moving an application to the cloud?

Request a migration plan consult. We will scope the move with you and come back with a fixed-scope plan.