Database Migration from OnPrem to AWS RDS

This project provides a step-by-step guide on how to migrate a WordPress website and MariaDB database from on-premises to AWS, using peering connections and AWS services such as EC2, RDS, and DMS. The guide covers setting up the simulated environment, …


This content originally appeared on DEV Community and was authored by Prakash Rao

This project provides a step-by-step guide on how to migrate a WordPress website and MariaDB database from on-premises to AWS, using peering connections and AWS services such as EC2, RDS, and DMS. The guide covers setting up the simulated environment, creating VPC and peering connection, launching instances, setting up DMS replication, and testing..

dms

Installation

To use this project, you need to have the following:

  • A simulated AWS on-prem env with a WordPress website and MariaDB database.
  • An AWS account with access to EC2, RDS, and DMS.

The guide covers the following steps:

  1. Assuming a simulated on-premises environment on AWS with a WordPress website and MariaDB database are already setup.
  2. Create an AWS VPC and peering connection between the on-premises (simulated) environment and the AWS VPC.
  3. Launch an EC2 instance in the AWS VPC and configure it as the new webserver for the WordPress website.
  4. Launch an RDS instance in the AWS VPC and configure it as the new database server for the MariaDB database.
  5. Set up DMS replication instance between the on-premises MariaDB database and the AWS RDS instance and start replicating.
  6. Test the migrated WordPress website by modifying the wordpress file where the ip is pointed to on-prem to DNS of MariaDB database.
  7. As a cleanup delete the instances, peering connection, DMS replication instance, RDS, EC2, etc.

Snipaste_2023-03-23_17-05-08
Snipaste_2023-03-23_17-06-28
Snipaste_2023-03-23_17-07-51
Snipaste_2023-03-23_17-08-34
Snipaste_2023-03-23_17-08-59
Snipaste_2023-03-23_17-16-40
Snipaste_2023-03-23_17-17-56
Snipaste_2023-03-23_17-19-07
Snipaste_2023-03-23_17-19-44
Snipaste_2023-03-23_17-20-41
Snipaste_2023-03-23_17-21-12
Snipaste_2023-03-23_17-21-39
Snipaste_2023-03-23_17-23-41
Snipaste_2023-03-23_17-26-10
Snipaste_2023-03-23_17-35-09
Snipaste_2023-03-23_17-38-33
Snipaste_2023-03-23_17-38-59
Snipaste_2023-03-23_17-40-16
Snipaste_2023-03-23_17-42-15
Snipaste_2023-03-23_17-43-14
Snipaste_2023-03-23_17-44-38
Snipaste_2023-03-23_17-46-20
Snipaste_2023-03-23_17-47-26
Snipaste_2023-03-23_17-47-43
Snipaste_2023-03-23_17-48-42
Snipaste_2023-03-23_17-49-56
Snipaste_2023-03-23_17-50-23
Snipaste_2023-03-23_17-51-54
Snipaste_2023-03-23_17-54-05
Snipaste_2023-03-23_17-54-41
Snipaste_2023-03-23_17-55-57
Snipaste_2023-03-23_17-56-16
Snipaste_2023-03-23_17-58-03
Snipaste_2023-03-23_17-58-17
Snipaste_2023-03-23_17-58-32
Snipaste_2023-03-23_17-59-05
Snipaste_2023-03-23_18-01-21
Snipaste_2023-03-23_18-01-59
Snipaste_2023-03-23_18-02-57
Snipaste_2023-03-23_18-03-52
Snipaste_2023-03-23_18-04-42
Snipaste_2023-03-23_18-06-48
Snipaste_2023-03-23_18-08-08
Snipaste_2023-03-23_18-10-56
Snipaste_2023-03-23_18-16-02
Snipaste_2023-03-23_18-17-12
Snipaste_2023-03-23_18-19-50
Snipaste_2023-03-23_18-23-02
Snipaste_2023-03-23_18-24-06
Snipaste_2023-03-23_18-24-40

Snipaste_2023-03-23_18-31-20
Snipaste_2023-03-23_18-32-03
Snipaste_2023-03-23_18-33-27
Snipaste_2023-03-23_18-34-00
Snipaste_2023-03-23_18-36-15
Snipaste_2023-03-23_18-36-40
Snipaste_2023-03-23_18-37-35
Snipaste_2023-03-23_18-37-52
Snipaste_2023-03-23_18-38-31
Snipaste_2023-03-23_18-42-38
Snipaste_2023-03-23_18-46-38
Snipaste_2023-03-23_18-47-13
Snipaste_2023-03-23_18-55-21
Snipaste_2023-03-23_18-55-50
Snipaste_2023-03-23_19-00-37
Snipaste_2023-03-23_19-01-04
Snipaste_2023-03-23_19-01-57
Snipaste_2023-03-23_19-02-44
Snipaste_2023-03-23_19-06-03
Snipaste_2023-03-23_19-07-38
Snipaste_2023-03-23_19-09-54
Snipaste_2023-03-23_19-12-56
Snipaste_2023-03-23_19-13-09

CleanUp:

At the end as a cleanup delete the instances, peering connection, DMS replication instance, RDS, EC2, etc.


This content originally appeared on DEV Community and was authored by Prakash Rao


Print Share Comment Cite Upload Translate Updates
APA

Prakash Rao | Sciencx (2024-08-31T16:10:25+00:00) Database Migration from OnPrem to AWS RDS. Retrieved from https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/

MLA
" » Database Migration from OnPrem to AWS RDS." Prakash Rao | Sciencx - Saturday August 31, 2024, https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/
HARVARD
Prakash Rao | Sciencx Saturday August 31, 2024 » Database Migration from OnPrem to AWS RDS., viewed ,<https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/>
VANCOUVER
Prakash Rao | Sciencx - » Database Migration from OnPrem to AWS RDS. [Internet]. [Accessed ]. Available from: https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/
CHICAGO
" » Database Migration from OnPrem to AWS RDS." Prakash Rao | Sciencx - Accessed . https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/
IEEE
" » Database Migration from OnPrem to AWS RDS." Prakash Rao | Sciencx [Online]. Available: https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/. [Accessed: ]
rf:citation
» Database Migration from OnPrem to AWS RDS | Prakash Rao | Sciencx | https://www.scien.cx/2024/08/31/database-migration-from-onprem-to-aws-rds/ |

Please log in to upload a file.



There are no updates yet.
Click the Upload button above to add an update.

You must be logged in to translate posts. Please log in or register.

Related Posts