Your company currently has a 2-tier web application running in an on-premises data center. You have
experienced several infrastructure failures in the past two months resulting in significant financial losses. Your
CIO is strongly agreeing to move the application to AWS. While working on achieving buy-in from the other
company executives, he asks you to develop a disaster recovery plan to help improve Business continuity in
the short term. He specifies a target Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective
(RPO) of 1 hour or less. He also asks you to implement the solution within 2 weeks. Your database is 200GB in
size and you have a 20Mbps Internet connection. How would you do this while minimizing costs?
Create an EBS backed private AMI which includes a fresh install or your application. Setup a script in your
data center to backup the local database every 1 hour and to encrypt and copy the resulting file to an S3
bucket using multi-part upload.
Install your application on a compute-optimized EC2 instance capable of supporting the application’s
average load synchronously replicate transactions from your on-premises database to a database instance in
AWS across a secure Direct Connect connection.
Deploy your application on EC2 instances within an Auto Scaling group across multiple availability zones
asynchronously replicate transactions from your on-premises database to a database instance in AWS across a
secure VPN connection.
Create an EBS backed private AMI that includes a fresh install of your application. Develop a Cloud
Formation template which includes your Mil and the required EC2. Auto-Scaling and ELB resources to support
deploying the application across Multiple-Ability Zones. Asynchronously replicate transactions from your onpremises database to a database instance in AWS across a secure VPN connection.