Platform Services



Customer  A leading mobile IOT solutions provider

Size  200+ users worldwide

project overview

Our client, a leading mobile IOT solutions provider, had their on-premise mobile solutions running in their primary Data Center in Oregon. In the event they had downtime issues with their applications, their basic disaster recovery approach was to failover to a secondary Data Center in Las Vegas. Data was synchronized between the two data centers using standard data backup mechanisms. This approach however did not scale very much as:

  • Procuring and provisioning new infrastructure was a nightmare thereby impacting
  • their overall time to market.
  • Recovery time objective (RTO) and Recovery point objective(RPO) were higher
  • leading to longer application downtime.
  • Resource Overheads to manage the resources in primary and secondary data
  • center were higher

The proposed architecture by Aplima was to run and maintain client’s mobile application

on a minimal footprint of Amazon EC2 Instances or AWS infrastructure (warm standby) to meet Customer’s required RTO and RPO.In the case of failure of the on-premise production system, the standby environment would be scaled up for production load , and DNS records would be changed to route all traffic to AWS.

As part of the design implementation:

  • Used Virtual Private Cloud to provision a logically isolated section of the AWS Cloud 
  • Set up OpenVPN and Bastion hosts to allow corporate users login to AWS
  • infrastructure
  • Created and maintained Amazon machine Images using t2.small instance type for
  • the web and application servers.
  • Set up CloudFormation templates to scale the infrastructure for production load.
  • Set up AWS RDS MySQL instance to replicate(mirror) data from on-premise MySQL
  • server.
  • Set up Elastic Load Balancers to distribute traffic to web and application servers.
  • Leveraged Simple storage service to store cloud formation templates and all logs.
  • In the event of a failover:
  • Used highly scalable and available Route 53 service to route end user requests to
  • infrastructure running in AWS.
  • Increased the size of the web and application EC2 instances in service with the ELBs.
  • Increased the size of the RDS MySQL database instance for the production load.
  • Created read replicas for increased performance.
  • Used CloudWatch and AutoScaling to monitor and right-size the fleet or
  • accommodate the increased load

Setting up warm standby disaster recovery in AWS drastically reduced the recovery times

by leveraging the minimal footprint running on AWS and quickly provisioning

pre-configured AMIs with the automated templates in the event of a disaster, all at a

fraction of cost of traditional DR approach.


  • Cost-effective DR solution
  • Scalable DR infrastructure
  • Failover capability
  • Minimal downtime


  • Detailed cost analysis on setting up a traditional DR site vs setting up a DR site in AWS.
  • Pre-configured AMIs
  • CloudFormation templates to scale the infrastructure to production load
  • Database mirroring to RDS
  • Failover capability
  • Monitoring and automated scaling
  • Documentation of new DR solution


  • Review of the existing infrastructure
  • Cost Analysis of DR solutions
  • Proof-of-Concept for proposed DR solution
  • Implementation of DR solution
  • Admin Training


  • A cost effective DR solution which
  • Was 55% lower than a traditional DR solution
  • Met Client’s Recovery Time Objective
  • Met Client’s Recovery Point Objective

learn how aplima can help you

Aplima Inc provides industry-wide best practices based design automation and training solutions for IT organizations. We specialize in helping e-businesses improve efficiency and reliability across their entire software Delivery Life cycle. Regardless of the size of their business, Aplima helps clients maximize the capabilities and the value of their technology organizations.


Get started by contacting our experts today!

For more information, visit our contact page or email us directly at