Backtrack Storage Pricing
Start course
4h 25m

This section of the AWS Certified Solutions Architect - Professional learning path introduces you to the AWS database services relevant to the SAP-C02 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 AWS Certified Solutions Architect - Professional exam. 

Want more? Try a Lab Playground or do a Lab Challenge

Learning Objectives

  • 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 which AWS database service to choose based on your requirements
  • Discover how to use automation to deploy databases in AWS
  • 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:

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. 

About the Author
Learning Paths

Danny has over 20 years of IT experience as a software developer, cloud engineer, and technical trainer. After attending a conference on cloud computing in 2009, he knew he wanted to build his career around what was still a very new, emerging technology at the time — and share this transformational knowledge with others. He has spoken to IT professional audiences at local, regional, and national user groups and conferences. He has delivered in-person classroom and virtual training, interactive webinars, and authored video training courses covering many different technologies, including Amazon Web Services. He currently has six active AWS certifications, including certifications at the Professional and Specialty level.