Designing for Disaster Recovery & High availability in AWS - Level 3

This course covers the core learning objective to meet the requirements of the 'Designing Network and Data Transfer solutions in AWS - Level 3' skill

Learning Objectives:

  • Evaluate advanced techniques to detect for failure and service recoverability
  • Create an automated, cost-effective back-up solution that supports business continuity across multiple AWS Regions
  • Evaluate different architectures to provide application and infrastructure availability in the event of an AWS service disruption

Before we jump into the console to see how easy it is to create backups for your AWS resources, let's go ahead and define our AWS backup commonly used terms. Backup rule. A backup rule simply specifies when and where to back up your data and what to do with it over time. So, using rules, you can manage schedules, retention policies and also cross account backups if you need them. Backup plan. A backup plan is an association of one or more rules to which you can assign resources. 

And a resource in this case is simply the item that you're trying to back up. It could be an EC2 instance, an on-prem virtual machine, an RDS database and so on. Vault. A vault is an AWS-managed encrypted storage location for all your backups. Vault lock. Putting a lock on your vault gives you the ability to meet compliance requirements for your data. This is because enabling vault lock ensures that your data cannot be re-encrypted which could happen in a ransomware attack for example. Locking your bolt follows the WORM model, which is write once read many. And finally, a job. A job is the action of creating a backup or restoring one following the backup plan. It's the way we track activity performed by AWS backup. That should be enough theory for now, let's get into the practice.


About the Author
Carlos Rivas
Sr. AWS Content Creator
Learning Paths

Software Development has been my craft for over 2 decades. In recent years, I was introduced to the world of "Infrastructure as Code" and Cloud Computing.
I loved it! -- it re-sparked my interest in staying on the cutting edge of technology.

Colleagues regard me as a mentor and leader in my areas of expertise and also as the person to call when production servers crash and we need the App back online quickly.

My primary skills are:
★ Software Development ( Java, PHP, Python and others )
★ Cloud Computing Design and Implementation
★ DevOps: Continuous Delivery and Integration