Scribd
Upload
242 views

AWS Project

The document discusses migrating an on-premises server infrastructure to AWS. It describes assessing the existing setup, planning a phased approach including rehosting some applications and refactoring a monolithic POS system into microservices. Post-migration the new environment was monitored and optimizations were made around performance and automation.

Uploaded by

venu
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
242 views

AWS Project

The document discusses migrating an on-premises server infrastructure to AWS. It describes assessing the existing setup, planning a phased approach including rehosting some applications and refactoring a monolithic POS system into microservices. Post-migration the new environment was monitored and optimizations were made around performance and automation.

Uploaded by

venu
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

AWS Project

In my initial assesment at Naidu Hall, I did a thorough SWOT about their IT


infrastructure and identified that their different business units were operating in
SILOs and were dependent on manual communications. And most importantly their
server setup was inefficient and outdated, which was affecting overall operational
efficiency.

So I wanted to unify the business data as one, and that needed introduction of new
products, but it needed a scalable but cost effective server, as the current server
was on premises and almost at its maximum capacity and it required frequent
hardware repairs due to its age. To tackle this and also to resolve the exisiting
issues with the onprim server, I iniitated a AWS migration of the server.

I led the initial assessment phase, collaborating with IT architects and business
stakeholders to evaluate our existing infrastructure and identify migration
candidates. Then I conducted feasibility studies to assess the compatibility of our
applications with AWS services and identify any potential challenges. I was able to
buy-in the stakeholders for migration, stating the need for scalability, cost-
efficiency, reliability, and leveraging cloud-native features like Amazon RDS
snapshots, S3 versioning, or cross-region replication can provide cost-effective
disaster recovery capabilities.

"So I formed the team with cloud skills and expertise and coordinated training
sessions and certification opportunities to enhance the team's AWS proficiency.
Based on the feasbility analysis, I decided on a mix of Rehositng and Replatfoming
strategy. Reason being, most of the applications used by the organization was
straight forward, that was compatible for lift and shift. But 50% of their server
utilization was by their POS software, which was monolithic.
I planned the migration in 4 phases
In first phase ,we implemented and managed the amazon VPC with careful
considerations and protocols for a secure network design using Terraform. For
security measures, we employed IAM roles and policies, security groups and ACLs.

The second phase comprises of the conversion of monolithic POS software to


microservices architecture. We analyzed the logical boundaries of the POS to
identify how and where it could be broken down. The microservices were encapsulated
with specific business capabilities, ensuring they were independently deployable.
We implemented Amazon API Gateway to manage, secure, and route requests to the
appropriate microservices.
These microservices were containerized in docker, and orchestrated with Amazon ECS
(Elastic Container Service) for easier management, scaling, and deployment.

"The third phase was decided to be more of a POC, so I picked up the applications,
particularly those that were less critical and we opted for a straightforward
Rehosting strategy. So we used AWS Server Migration Service (SMS) to automate the
migration of virtual machines from VMware to Amazon EC2 instances.Then used
replatform strategy for database migration. We used cloudberry to backup and
migrate databases from SQL server to S3 and then to Amazon RDS,

In the final phase we continued the same for remaining microservices app.

Post Migration, we monitored the server for 4 weeks to analyze stability and
performance using cloudwatch. We ran the migrated applications in a sandbox
environment to benchmark their performance against the on-prim setup and tested the
security controls, data protection mechanisms and compliance. We used AWS auto
scaling to optimize performance.
Finally, to ensure faster and reliable delivery we established a CI/CD pipline
using AWS code build and automated the build, test and deployment processes with
AWS code pipeline incorporating extensive automated tests including unit,
integration, and performance tests, to maintain code quality and reliability.

With this, we were successfully able to migrate our server from on-prim to AWS.

You might also like