In a real-world scenario, I served as the Cloud Specialist spearheading the migration of a workload from a Corporate Data Center to AWS. My role encompassed orchestrating the seamless transition of both the application and database to the AWS platform. Employing the Lift & Shift (rehost) model, we transferred not only the application itself but also ensured the smooth relocation of all associated database data.
I meticulously adhered to a structured set of migration steps, beginning with comprehensive planning. This entailed meticulously sizing resources, establishing prerequisites, and implementing meticulous resource naming conventions. During the execution phase, I oversaw the seamless provisioning of resources while adhering to industry best practices to optimize performance and efficiency.
The critical stages of go-live were meticulously managed, encompassing validation tests such as dry-runs and ultimately executing the final migration, known as the cutover. Post go-live, I diligently ensured the operational integrity of the application and maintained uninterrupted user access, thus ensuring a successful transition to the AWS environment.
I established a Virtual Private Cloud (VPC) on AWS and provisioned both public and private subnets within it. The application server was deployed in the public subnet, while the database server was situated in the private subnet, all within the same Availability Zone.
For database migration, I extracted a SQL dump from the legacy server, then proceeded to create an RDS instance. Using the RDS endpoint, I connected from the EC2 instance, created a new database, user, and granted appropriate privileges.
Commands included:
show databases;
create database db_name;
show databases;
use db_name;
show tables;
source dump.sql;
show tables;
select * from table_name;
For user management:
CREATE USER username@'%' IDENTIFIED BY 'pwd;
GRANT ALL PRIVILEGES ON database.* TO username@'%';
FLUSH PRIVILEGES;
EXIT;
Concluding the process, I executed the application run file to deploy and initiate the application on the newly provisioned AWS infrastructure. Application was performing as desired. It was performing transaction on RDS by populating DB and retrieving the data from RDS DB as expected.
Comments