This advanced demo consists of 5 steps :-
- STEP 1 : Provision the environment and review tasks
- STEP 2 : Establish Private Connectivity Between the environments (VPC Peer)
- STEP 3 : Create & Configure the AWS Side infrastructure (App and DB)
- STEP 4 : Migrate Database & Cutover <= THIS STAGE
- STEP 5 : Cleanup the account
https://console.aws.amazon.com/dms/v2/home?region=us-east-1#subnetGroup
Click Create Subnet Group
For Name and Description use A4LDMSSNGROUP
for VPC choose awsVPC
for Add Subnets choose aws-privateA and aws-privateB
Click Create subnet group
Move to the DMS Console https://console.aws.amazon.com/dms/v2/home?region=us-east-1#replicationInstances
Click create Replication Instance
for name enter A4LONPREMTOAWS
use the same for Description
for Instance Class choose dms.t3.micro
for VPC choose awsVPC
Uncheck MultiAZ and Pubicly Accessing
Expand Advanced security and network configuration
Ensure a4ldmssngroup is selected in Replication subnet group
For VPC security group(s) choose ***-awsSecurityGroupDB-***
Click Create
Move to https://console.aws.amazon.com/dms/v2/home?region=us-east-1#endpointList
Click Create Endpoint
For Endpoint type choose Source Endpoint
Under Endpoint configuration set Endpoint identifier to be CatDBOnpremises
Under Source Engine set mariadb
Under Access to endpoint database choose Provide access information manually
Under Server name use the privateIPv4 address of CatDB (get it from EC2 console)
For port 3306
For username a4lwordpress
for password user the DBPassword you noted down in step 1
click create endpoint
Move to https://console.aws.amazon.com/dms/v2/home?region=us-east-1#endpointList
Click Create Endpoint
For Endpoint type choose Target Endpoint
Check Select RDS DB Instance
Select a4lwordpress in the dropdown
It will prepopulate the boxes
Under Access to endpoint database choose Provide access information manually
For Password enter the DBPassword you noted down in step1
Scroll down and click Create Endpoint
Move to migration tasks https://console.aws.amazon.com/dms/v2/home?region=us-east-1#tasks
Click Create task
for Task identifier enter A4LONPREMTOAWSWORDPRESS
for Replication instance pick the replication instance you just created
for Source database endpoint pick catdbonpremises
for Target database endpoint pick a4lwordpress
for Migration type pick migrate existing data you could pick and replicate changes here if this were a high volume production DB
for Table mappings pick Wizard
Click Add new selection rule
in Schema box select Enter a Schema
in Schema Name type a4lwordpress
Scroll down and click Create Task
This starts the replication task and does a full load from catdbonpremises to the RDS Instance.
It will create the task
then start the task
then it will be in the Running State until it moves into Load complete
At this point the data has been migrated into the RDS instance
Move to the RDS Console https://console.aws.amazon.com/rds/home?region=us-east-1#
Click Databases
Click a4lwordpress
under Endpoint & Port copy the endpoint dns name into your clipboard
Move to the EC2 console https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Instances:
Select the awsCatWeb instance, right click, Connect
Select Session Manager and click Connect
When connected type sudo bash to run a privileged bash shell
run cd /var/www/html
run nano wp-config.php
locate the define DB_HOST line, and reolace the IP address with the RDS Host you just copied down into you clipboard
run ctrl+o to save and ctrl+x to exit.
Run the script below, to update the wordpress database with the new instance DNS name
#!/bin/bash
source <(php -r 'require("/var/www/html/wp-config.php"); echo("DB_NAME=".DB_NAME."; DB_USER=".DB_USER."; DB_PASSWORD=".DB_PASSWORD."; DB_HOST=".DB_HOST); ')
SQL_COMMAND="mysql -u $DB_USER -h $DB_HOST -p$DB_PASSWORD $DB_NAME -e"
OLD_URL=$(mysql -u $DB_USER -h $DB_HOST -p$DB_PASSWORD $DB_NAME -e 'select option_value from wp_options where option_id = 1;' | grep http)
HOST=$(curl http://169.254.169.254/latest/meta-data/public-hostname)
$SQL_COMMAND "UPDATE wp_options SET option_value = replace(option_value, '$OLD_URL', 'http://$HOST') WHERE option_name = 'home' OR option_name = 'siteurl';"
$SQL_COMMAND "UPDATE wp_posts SET guid = replace(guid, '$OLD_URL','http://$HOST');"
$SQL_COMMAND "UPDATE wp_posts SET post_content = replace(post_content, '$OLD_URL', 'http://$HOST');"
$SQL_COMMAND "UPDATE wp_postmeta SET meta_value = replace(meta_value,'$OLD_URL','http://$HOST');"
Move to the EC2 console https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Instances:
Select CatDB, right click, instance state, stop instance stop
Move to the EC2 console https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Instances:
Select CatWeb, right click, instance state, stop instance stop
Move to the EC2 console https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Instances:
Select awsCatWeb and get its Public IPv4 DNS
Open this in a new tab
It should still show the application ... this is now pointed at the RDS instance after a full migration
At this point you have created a VPC peer between the simulated On-premises environment and AWS
You have fully migrated the wordpress application files from on-premises (simulated) into AWS
You have provisioned an RDS DB Instance
And you have used DMS to perform a simple migration of the database from on-premises (simulated) to AWS