RDS vs. EC2
Amazon RDS Costs
Data Lakes in AWS
The course is part of this learning path
This section of the Solution Architect Associate learning path introduces you to the AWS database services relevant to the SAA-C03 exam. We then understand the service options available and learn how to select and apply AWS database services to meet specific design scenarios relevant to the Solution Architect Associate exam.
Want more? Try a lab playground or do a Lab Challenge!
- Understand the various database services that can be used when building cloud solutions on AWS
- Learn how to build databases using Amazon RDS, DynamoDB, Redshift, DocumentDB, Keyspaces, and QLDB
- Learn how to create Elasticache and Neptune clusters
- Understand AWS database costs
- Learn about data lakes and how to build a data lake in AWS
Let me now move on to backtrack storage costs with Amazon Aurora. Backtrack is a feature that is only currently available for a MySQL-compatible Aurora database, using and is configured at the time of the database creation. Essentially, backtrack allows you to go back in time on the database to recover from an error or incident without having to perform a restore or create another DB cluster. For a deeper dive on on Backtrack storage, take a look at this AWS blog post found here: https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-turn-back-time/
As you can see from the configuration page during the Aurora database creation process, it is enabled via a checkbox and allows you to enter a number in hours of how far you would like to ‘backtrack’ to, with a maximum of 72 hours. In this example, I have entered 12 hours, and so Aurora will retain log data of all changes 12 hours as specified. The number of changes made directly relates to how much the Backtrack feature is going to cost you.
The pricing shown here is based upon a set cost per 1 million change records per hour for the London region.
So let’s look at an example. If you had built an Aurora database with a 12 hour backtrack setting like I had in my previous example that was generating 50,000 change records per hour the calculation would be as follows:
Obtain the total number of change records for your backtrack time period:
50,000 (change records/hour) x 12 hours = 600,000 change records
Calculating total costs based upon the London region:
(600,000 / 1,000,000) x $0.014 = $0.0084/hour
To help you keep an accurate record of the number of change records, you can use Amazon CloudWatch to help you monitor the number of change records that are being generated each hour.
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.