Indira IVF achieved scalability, performance, and reduction in cost by migrating their on-premises workload to AWS Cloud.

As their workloads on-premises were being run on both Windows and Linux-based OS, they required the same to be provisioned on AWS as well for their respective projects containing multiple Production & UAT environments.

They further needed an alternative for a workaround on a database solution offering for a few projects that included features like platform-managed by AWS, automatic scaling up/down, patching-like features, and support for automatic backups on a daily basis.

To find a scalable & reliable infrastructure by re-hosting & re-architecting some of their existing applications to support migration of it to AWS.

Seeking a cost-effective solution for their workload while ensuring security compliance is taken care of.

In the Assess phase, the Pentagon team extensively evaluated their current applications, dependencies, and infrastructure by utilizing the AWS Application Discovery Service to analyze their on-premises applications and collect essential data for the migration procedure. The service aided in identifying interconnections between applications, resource usage, and performance measurements. This evaluation yielded valuable information about the migration’s intricacy and prerequisites.

During the Mobilize phase, the Pentagon team initiated the preparations for the migration by establishing the essential AWS infrastructure and services by employing the AWS Application Migration Service to build a destination environment within AWS, which involved configuring the necessary resources like virtual machines, storage, networking, and security groups. This service enabled the replication of on-premises applications in the cloud, guaranteeing a seamless transition.

Migration of the infrastructure was completed by using AWS Application Migration Service for the application as well as the databases hosted on EC2 servers and AWS Database Migration Service for migrating databases to be hosted on Amazon RDS and Amazon Aurora clusters.

Each project environment in the AWS cloud was assigned a separate Amazon Virtual Private Cloud (Amazon VPC) network, and public/private subnets were created based on requirements.

Amazon EC2 instances were launched to host the applications specific to each project.

To establish network connectivity within the Amazon VPC environment, we deployed the Internet Gateway, route table, and NAT gateway accordingly.

PaaS solutions like Amazon RDS and Amazon Aurora for MySQL were launched in single and multi-AZ configurations to meet the environment’s needs.

To ensure the highest security measures, a Bastion Host was deployed in the public subnet of each project. This ensured that only authenticated users had access to the Production application and DB servers.

Application Load Balancers (Elastic Load Balancers) were deployed and configured in the environments and associated with the EC2 instances. This allowed external users to access the applications over the Internet.

Security groups for the EC2 instances were configured, and Inbound/Outbound rules were updated based on client requirements.

To enable connectivity between the client’s on-premises location and the AWS network, we created and configured a site-to-site VPN tunnel using a Virtual Private Gateway.

To enhance security, we implemented WAF and Shield in the AWS environment. This protected against common types of attacks at the Networking & Transport layer (Layers 3 & 4) and provided options for whitelisting.

Amazon CloudWatch was enabled as a monitoring service to ensure the health of the EC2 instances.

Backup policies were configured for the EC2 instances, and the data was stored as Amazon EBS Snapshots. Additionally, a copy of the data was maintained within Amazon S3 storage.

To meet compliance requirements and enable auditing, we enabled AWS CloudTrail to log all API calls made to AWS resources. The corresponding data was stored in Amazon Simple Storage Service (Amazon S3).

For data recovery purposes, AMI backups were created for the deployed servers, along with EBS Snapshots.

System Manager was set up to manage custom alerts and SSM roles.