Date: April 28, 2022

Time: 12 pm ET

Don’t succumb to normalcy bias, we often underestimate the worst case scenario. Disasters come in all forms which directly impact end-users. While rare, all organizations need to plan for IT disasters such as regional unavailability, data corruption, third party software failures, or even cyber-attacks. These events can not only disrupt the business, but also cause data loss, impact revenue, and damage your software's reputation.

Work on disaster recovery and high availability starts by tiering your workloads and defining the recovery time objectives (RTO) and recovery point objectives (RPO) for each tier. A disaster recovery (DR) strategy is then created by defining objectives such as: backup and restore, active/passive (pilot light or warm standby), or active/active.

AWS can help customers solve for disaster recovery and high availability requirements through the use of services such as Amazon Route53 and Route53 Application Recovery Controller (ARC), Amazon S3 and S3 Glacier, Amazon EFS, Amazon RDS, DynamoDB Global Tables, and Amazon EBS.

We’ll cover: 

• Opportunity cost of not architecting for high availability and how DR strategies can reinforce high availability and performance
• Overview of RTO & RPO and crisis response plans as well as crisis preparation activities  
• Technical options available for DR and per workload DR capabilities (compute tier, data tier, and storage tier).
• Customer success story on how a Fintech startup achieved DR maturity through incremental improvements
• Open Q/A