In this course, you will learn how to use AWS Backup to create snapshots and have them available in another region — essentially creating a Disaster Recovery site.
- Have a greater understanding of the AWS Backup service and how it interacts with other services such as EC2, EBS, and RDS
- See how we create a cross-region backup
- Terminology of AWS Backup
- Basic usage
- Creating a Backup Plan
- Enabling and verifying cross-region functionality
- Those who want to understand the basics of the AWS Backup service
- Those ready to tackle the hands-on task of creating EC2 snapshots that could be used to recover from an outage
- Those who manage a fleet of EC2, perhaps along with RDS for their databases
- Have an understanding of the basics of AWS, such as using EC2 for Virtual Machines and RDS for your databases. As long as you understand how those services work at a high level, you should be able to get the most out of this course.
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.
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