Resources / Case Studies

Developing a Warm Standby Disaster Recovery Plan

Our team worked with this customer to develop a disaster recovery plan leveraging AWS Elastic Disaster Recovery.

The Customer

Our customer is a US-based brand that provides world-class vertical transportation services at the local, regional, and national level.

The Challenge

The customer uses Liftkeeper as its Elevator Service Management Software. Liftkeeper, a SaaS solution, was hosted in the Liftkeeper AWS account without a Disaster Recovery solution. To comply with their resiliency requirements and further bolster their existing business continuity plan with fast recovery times, the customer sought a partner to design and implement a Disaster Recovery solution for the software. 

Why AWS?

The Liftkeeper SaaS Application was already in AWS, using EC2, Aurora RDS, EFS, S3, and Elasticache. Choosing AWS for a disaster recovery solution was a natural extension of the customer’s investment in the cloud provider. JetSweep designed a DR solution using AWS DRS to take advantage of the benefits of a native solution.

Why JetSweep?

The customer wanted to work with an AWS Partner to support their Disaster Recovery solution. Their team chose JetSweep because of our deep experience with resiliency and disaster recovery across AWS Services.

The Solution

During the initial planning phase, our team gathered information about the customer’s business, financial, and technical needs during stakeholder interviews. After meeting with the customer and Liftkeeper, their SaaS provider, our team recommended a Warm Standby approach in a different region to meet their RTO and business continuity requirements.

After choosing a DR Region, Liftkeeper granted JetSweep access to the region in their AWS account. JetSweep implemented AWS Elastic Disaster Recovery for AWS EC2 DR, AWS S3 Cross-Region Replication. The AWS Aurora RDS was converted to an AWS Aurora Global Database with the secondary cluster in the DR Region. AWS EFS Replication was configured with an EFS File System in the DR Region. Liftkeeper was using AWS Elasticache Memcached which does not support Disaster Recovery and as Elasticache is only used to store Session State, AWS Elasticache was deployed into the DR Region. AWS Security Groups and Application Load Balancers were pre-deployed into the DR Region.

Our team created and delivered a custom DR Runbook for the customer, which includes specific timelines, procedures, and responsibilities for all stakeholders in a disaster recovery scenario.

The Results and Benefits

Our customer was able to document that they had a Disaster Recovery Solution for their main business application for their board and new investors. The new solution meets all their business continuity requirements and ensure a near-zero RPO and RTO under two hours.

AWS Services

AWS Elastic Disaster Recovery

AWS RDS Aurora



AWS Application Load Balancer


AWS Elasticache

Let's get to talking.