ModMed Institute Cloud Migration and Disaster Recovery

 

Problem Definition

ModMed Institute is a well-known profit-for-purpose enterprise dedicated to improving lives through health education.

With the ongoing, rapid changes to technology and cyber-security, ModMed Institute commissioned Comunet to perform an initial security review of their current application and hosting arrangements for delivery of their services and platform.

Through this engagement, several key opportunities to reduce risk and enhance security and business continuity / disaster recovery positions were identified.  A significant part of these findings included moving from the current incumbent hosting environment to AWS.

Proposed Solution & Architecture

Comunet proposed a new architecture, both for the application and Infrastructure-as-a-service (IAAS) design which more clearly segregated Development, Testing and Production environments with a focus on robust, easily recoverable production environments.

Defining appropriate Recovery Point, and Recovery Time Objectives (RPO/RTO) ModMed Institute and Comunet worked together to find the best balance of cost to business needs on AWS.  Finalisation of this included the architecture and documentation of a full Disaster Recovery Plan covering both technical and non-technical aspects that could be easily followed if an event occurred.

Utilising primarily AWS Elastic Compute Cloud (EC2) with Amazon CloudWatch and other 3rd party monitoring applications, AWS would become the core hosting platform for ModMed Institute’s Software-As-A-Service (SAAS) model for future clients.

Project Outcomes & Success Measures

After successful migration of ModMed Institute’s core environments to AWS, ModMed Institute have been able to show their clients a robust, secure, recoverable solution that has significantly increased client / vendor confidence and trust.

Lessons Learned 

With existing applications hosted elsewhere – there are always complexities with custom scripting, services and 3rd party applications that can cause risks in a migration such as this.  By performing a full development and UAT environment build, migration and refresh approach – these risks were offset allowing a clean migration for the production workloads.