📋 Introduction
Migrating databases from on-premises to AWS is a critical step in cloud adoption. AWS Database Migration Service (DMS) helps streamline this process by providing a secure, scalable, and automated solution for full-load and ongoing replication of databases.
Following Phase 1 - Application Discovery & TCO Analysis, we now move to Phase 2: AWS Database Migration to efficiently transition MySQL databases from an on-premises setup to Amazon RDS (Relational Database Service).
📌 Key Objectives of Phase 2
✅ Provision AWS RDS as the target database.
✅ Create a DMS Replication Instance to facilitate data migration.
✅ Configure Source & Target DMS Endpoints for secure connections.
✅ Enable Binary Logs in MySQL for ongoing replication.
✅ Execute AWS DMS Migration Task for database replication.
By the end of this phase, the on-prem MySQL database will be fully migrated to AWS RDS, ensuring data integrity, security, and scalability.
📑 Follow the GitHub Documentation for Full Details
🔹 GitHub Repo: AWS Migration Project
📌 Phase 2: AWS Database Migration
➡️ Pre-Requisite: GitHub Link
➡️ Database Migration: GitHub Link
➡️ Troubleshooting: GitHub Link
🔹 🎥 Watch the Video Tutorial on YouTube: Click Here
🌍 On-Premises Database Overview
Before migration, let’s understand the existing on-prem database setup:
📌 Database Server Details
🔹 Database: MySQL 5.7
🔹 Operating System: Ubuntu 24.04 LTS
🔹 Storage: 8 GB SSD
🔹 Tables: obbs.tbladmin, obbs.tblbooking, obbs.tblcontact, etc.
🔹 Replication Type: Full Load + Ongoing Replication (CDC)
💡 Challenges with On-Premises Databases:
❌ High Maintenance Costs – Requires manual upgrades and monitoring.
❌ Limited Scalability – Hard to scale with increasing data load.
❌ Backup & Recovery Issues – No automated snapshot capabilities.
✅ Why AWS RDS?
✔️ Fully managed database with automated backups.
✔️ High availability with Multi-AZ deployment.
✔️ Auto-scaling capabilities for dynamic workloads.
🏗 Step 1: Create Target RDS Database in AWS
📌 The first step is to provision an Amazon RDS MySQL instance as the target database.
🛠 Steps to Create RDS Instance
1️⃣ Go to AWS Console → Amazon RDS → Create Database
2️⃣ Select MySQL as Engine Type
3️⃣ Choose Multi-AZ Deployment for High Availability
4️⃣ Set Master Username & Password
5️⃣ Configure Security Groups for Database Access
6️⃣ Enable Automated Backups & Monitoring
7️⃣ Click on Create Database
📌 Once the RDS instance is running, note the endpoint.
✅ Example: database-1.cpioo8iee1me.us-west-2.rds.amazonaws.com
🚀 Step 2: Create AWS DMS Replication Instance
📌 AWS DMS Replication Instance acts as a bridge to replicate data from the source MySQL database to Amazon RDS.
🛠 Steps to Create a DMS Replication Instance
1️⃣ Go to AWS DMS Console → Replication Instances → Create Replication Instance
2️⃣ Choose Instance Type: dms.t3.medium (for moderate workloads)
3️⃣ Set Storage: 100 GB (adjust based on database size)
4️⃣ Select VPC & Security Groups: Ensure RDS and On-Prem Server are accessible
5️⃣ Click Create Replication Instance
📌 Once the replication instance is available, proceed to configuring endpoints.
🔹 Source Endpoint (On-Prem MySQL)
1️⃣ Go to AWS DMS Console → Endpoints → Create Endpoint
2️⃣ Choose Source Type: MySQL
3️⃣ Enter Source Database Endpoint: <on-prem-db-IP>:3306
4️⃣ Enter Username & Password
5️⃣ Test Connection → If Successful, Save Endpoint
🔹 Target Endpoint (Amazon RDS MySQL)
1️⃣ Go to AWS DMS Console → Endpoints → Create Endpoint
2️⃣ Choose Target Type: MySQL
3️⃣ Enter Amazon RDS Endpoint: database-1.cpioo8iee1me.us-west-2.rds.amazonaws.com
4️⃣ Enter Username & Password
5️⃣ Test Connection → If Successful, Save Endpoint
✅ With both endpoints successfully configured, we move to DMS Migration Task.
🚀 Step 4: Execute DMS Migration Task
📌 Create a migration task in AWS DMS to transfer data from On-Prem MySQL to AWS RDS.
🛠 Steps to Create DMS Migration Task
1️⃣ Go to AWS DMS Console → Database Migration Tasks → Create Task
2️⃣ Select Source & Target Endpoints
3️⃣ Choose Replication Type: Full Load + Ongoing Replication (CDC)
4️⃣ Enable Logging & CloudWatch Monitoring
5️⃣ Click Start Migration Task
📌 DMS will now start migrating the data. Check CloudWatch logs for progress.
Status: Created
Status: Load Complete
✅ Step 5: Testing & Validation
📌 Once migration is complete, validate the database in AWS RDS.
🛠 Steps to Verify Data Migration
1️⃣ Connect to AWS RDS using MySQL Workbench or CLI.
mysql -h database-1.cpioo8iee1me.us-west-2.rds.amazonaws.com -u admin -p
2️⃣ Check database and tables.
SHOW DATABASES;
USE obbs;
SHOW TABLES;
3️⃣ Verify Data Consistency
SELECT COUNT(*) FROM obbs.tbladmin;
✅ Data successfully migrated from on-prem to AWS RDS! 🎉
🎯 Summary of Phase 2
✅ Provisioned AWS RDS MySQL as the Target Database.
✅ Created AWS DMS Replication Instance for Data Transfer.
✅ Configured Source & Target Endpoints for Secure Migration.
✅ Executed DMS Migration Task for Full Load & Ongoing Replication.
✅ Verified Data Consistency Post-Migration.
📌 Next Step: Phase 3 - Application Migration
🔗 GitHub Repo: AWS Migration Project
🎥 Watch on YouTube: Click Here
🚀 Stay tuned for more AWS migration insights!
#AWS #DMS #DatabaseMigration #CloudComputing #DevOps #RDS #AmazonWebServices
