Designing for Failure
Managing RTO and RPO for AWS Disaster Recovery
Designing for high availability, fault tolerance and cost efficiency
High Availability in RDS
High Availability in Amazon Aurora
High Availability in DynamoDB
The course is part of this learning path
This section of the Solution Architect Associate learning path introduces you to the High Availability concepts and services relevant to the SAA-C03 exam. By the end of this section, you will be familiar with the design options available and know how to select and apply AWS services to meet specific availability scenarios relevant to the Solution Architect Associate exam.
Want more? Try a lab playground or do a Lab Challenge!
- Learn the fundamentals of high availability, fault tolerance, and back up and disaster recovery
- Understand how a variety of Amazon services such as S3, Snowball, and Storage Gateway can be used for back up purposes
- Learn how to implement high availability practices in Amazon RDS, Amazon Aurora, and DynamoDB
Let’s perform a quick demonstration of requesting a Point In Time Recovery. I’ll perform the demonstration within the AWS Dynamodb console. The first thing that we need to do is enable Point In Time Recovery on the “cloudacademy-courses” table.
To do so I’ll select the table and then navigate into the backups tab. Here, under the Point In Time Recovery section I’ll click the Enable option to enable it. Once it has been enabled take note of the earliest and latest restore dates - these are the parameters that your point in time recovery must be requested within.
It's important to note that the Latest restore date always lags the current time by a few minutes. Let's now examine the local system clock within the terminal to determine the current time. Next, I’ll return to the “cloudacademy-courses” table and delete one of the existing items. Returning back to the backups section I’ll perform an immediate Point In Time Recovery - and name it “pitr-recovery1”. I’ll then return to backups of the same table and wait until the latest restore date moves beyond the time that I just made the delete - when this ready I’ll take a second Point In Time Recovery - and name it “pitr-recovery2”.
I’ll now skip the demo forward to the point where both Point In Time Recovery tables have been successfully restored.
Here we can see that the first point in time recovery table still contains the table item that I deleted. This is because the latest restore date at the Point In Time Recovery request hadn’t moved beyond the time at which I performed the item deletion.
If we now view the second point in time recovery table we can see that it indeed contains all but the deleted item. This is because the latest restore date at the Point In Time Recovery request had now moved beyond the time at which I performed the item deletion.
This highlights the concept of automated point in time recovery - a very cool and useful table data recovery feature!
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.