KIMS Hospital had Internal facing HIMS application and other in-house application running in an on-premises data center for approximately 600 users consisting of Administration, Accounts and Finance department, Doctors and pharmacists. They experienced frequent outages and failures in the past few months, which led to a significant loss in the business productivity. KIMS agreed to move the business-critical workloads to cloud. They also wanted to achieve the business continuity without much impact on the RPO and RTO.
Redington carried out a thorough assessment of KIMS on-premises data center, studied the environment clearly and a detailed inventory list was prepared by having the following parameters in the infrastructure:
Number of servers to be moved
Different types of operating system and evaluation of security at the operating system level
Processor and memory required for the application, user concurrency and various utilization levels.
Storage growth rate, utilization, and configuration
Methodologies and frequency of backup and restore requirements.
In an application review process, Redington identified the applications could be transitioned based on the buyer’s:
Integration and dependencies points
Performances of the applications
Remote access disk consumption and
The growth rate of the user with a clear road map towards the cloud.
Redington as part of the implementation best practice followed the CIS guidelines throughout the implementation. Effectively using AWS Services like cloud watch and cloud trail to monitor and protect the complete AWS resources, secure the data in motion and at rest, AWS Managed encryption along with key storage and key management. Redington established a IPSEC VPN connection between KIMS Data center and AWS using the virtual private cloud to enable secure communication between point to point.
KIMS agreed to Redington’s suggestion of moving 80 percent of the KIMS business-critical workload to cloud. By using the VM import and export migration service in AWS, the Virtual machines were migrated to the AWS S3 storage and from the S3 storage the EC2 instances were launched. All the EBS volumes were encrypted so that snapshots of the volumes too were encrypted to keep up the security in priority as per the KIMS Requirement.
The on-premises environment had no backup and DR strategy in place. On AWS, the Redington Team had configured automatic scripts to create snapshots of every volume and store them in Amazon simple storage service for the nightly backups of data.
10 TB of archival data present in the on-premises SAN storage needs to be backed up to Amazon S3. For backup of this data, cloudberry tool was used to back up to Amazon S3 frequently. Using the Amazon S3 lifecycle policies, the data was moved to glacier to optimize the cost of the storage.
By migrating the workload to Cloud, availability of the workload was achieved.
By moving to cloud, operation tasks like monitoring and log analysis, backing up of the data etc. have been automated and reduced the repetitive tasks.
Low-cost backup strategy was implemented to protect their data using AWS storage like S3 and glacier. This saved over 60 percent of cost compared to the proposed on-premises backup solution. Additionally, the availability and durability of the backed-up data also increased multi-fold.