Emergency Communications Firm Migrates AWS Regions with 100% Uptime
It’s not an understatement to say that uptime for this provider’s emergency communications services, can spell the difference between life and death. Communicating with people during critical events to keep them safe, informed and connected, this company had a need to maintain its 100 percent up time, security and availability as it grew. The DevOps team here at Flux7 were glad to take the call to give them a hand.
This emergency service firm had a positive business challenge: how to maintain its quality of service while keeping up with business growth. While the company had an AWS setup in the California region, the team was excited about new features that had been made availaible in the Virginia region — features like Lambda and DataPipeline. The team was interested in taking advantage of these new features which meant a migration from their AWS CA Region to the VA Region.
While the company’s technology team is very savvy and could have executed the AWS regions migration themselves, with a thriving business, they had limited time for extra projects and as a result, called in the AWS Premier Consulting Partners at Flux7. As the communications solution is meant to work in an emergency, the migration needed to be seamless without any downtime. It needed to be flawlessly executed, which meant lots of testing before the move to ensure 100 percent confidence in the migration.
AWS Best Practices
In addition, the Flux7 team proposed that the migration could be more than just access to new AWS services, but an opportunity to introduce AWS best practices, and create other business improvements. As a result, with the migration Flux7 introduced the customer team to DevSecOps AWS best practices such as the use of AWS CloudFormation, AWS Service Catalog and Infrastructure as Code for Disaster Recovery.
The migration strategy was to move one component at a time to the VA Region. From here, the team would point to a public DNS in CA, confirm it is working and then move to the next component to move. In this way the team was able to move lower risk items first, ensuring success before moving higher risk items.
For infrastructure deployment, Flux7 used AWS CloudFormation templates and Service Catalog portfolios. The CloudFormation and Service Catalog solution helped achieve a specific goal of the team: one-click infrastructure deployments. Now with the push of a button, developers can create and deploy an environment. Moreover, they are able to do so without depending on IT queues or affecting the production or QA environment. Now all individuals have access to the AWS resources they need to create needed infrastructure.
Another goal of the communication company’s team was to ease its Disaster Recovery (DR) deployment using Infrastructure as code. Using AWS CloudFormation templates, Flux7 and the organization’s team were able to easily provision and manage the DR infrastructure. In fact, they can easily manage any changes from here and with automation, ensure configurations are set appropriately to avoid against manual errors that could cause security issues down the road.
As with many Flux7 engagements, the team assessed, built and set-up the solution, providing the customer with the keys to facilitate the migration themselves. In addition to a thorough knowledge transfer with the migration, the company has grown its DevSecOps AWS practices, embracing CloudFormation and Service Catalog for greater automation and self-serve IT as well as growing the flexibility and security of its Disaster Recovery. For further detail on our work, please check out the full AWS case study here.