New CloudFormation Template - Backing up DynamoDB the easy way

Michael Wittig – 08 Aug 2017

DynamoDB is an easy-to-use NoSQL database available only on AWS. It comes with many useful features such:

  • Time-to-live for items
  • Secondary indexes
  • Scalable read and write throughput
  • Streams that contain all changes of a table

Unfortunately, there is no backup feature. You might say:

But DynamoDB replicates my data. The durability guarantees are super high. I will never lose my data. I can even replicate my data cross region

But what if your application has a bug and updates many items in a way that corrupts your data, or what if your cleanup script deletes the wrong items? You can not revert changes easily in DynamoDB. You need a backup in that case!

One of the solutions is to run a job on an EMR cluster that does the backup. But this is a multi-step process:

Andreas and Michael Wittig

Please support our work!

We have published 327 articles, 41 podcast episodes, and 15 videos. It's all free and means a lot of work in our spare time.

Thanks to Alan Leech, Alex DeBrie, e9e4e5f0faef, Goran Opacic, jhoadley, Shawn Tolidano, Thorsten Hoeger, Todd Valentine, Vince Fulco, and all anonymous supporters for your help! We also want to thank all supporters who purchased a cloudonaut t-shirt. It gives us great pleasure to send our t-shirts all over the world.

With your help, we can continue to produce independent & high-quality content focused on AWS. Please support us!

Support us
  1. Create an EMR cluster
  2. Wait until the cluster is ready
  3. Run the backup job
  4. Wait until the job is completed, retry if necessary
  5. Terminate the EMR cluster
  6. Wait until the cluster is terminated

Luckily, Data Pipeline is a service that can do the orchestration work for you. The Data Pipeline documentation has examples to backup and restore a DynmoDB table.

The only unsolved problem is: How to setup the Data Pipeline? My answer is CloudFormation. I authored a template to backup a DynamoDB table. The template contains the data pipeline, S3 buckets for logs and the backups, and also the glue to alert you if the backup fails. The following figure shows the pipeline definition:

Data Pipeline to backup a DynamoDB table

If you want to setup a CloudFormation stack to backup a DynamoDB table, just follow the steps in the Free Template for AWS CloudFormation documentation.

One downside of this solution is that you have to spin up an EMR cluster for each table that you backup. A cluster consists of one master and one core node, e.g. of type m4.large. In us-east-1 this means 2 * $0.10 (assuming the backup completes within one hour). Additionally, you pay for EMR 2 * $0.03 (also assuming the backup ti finish in under 1 hour). In total, you spend $0.26 per table per backup.

Michael Wittig

Michael Wittig

I launched cloudonaut.io in 2015 with my brother Andreas. Since then, we have published hundreds of articles, podcast episodes, and videos. It’s all free and means a lot of work in our spare time. We enjoy sharing our AWS knowledge with you.
Have you learned something new by reading, listening, or watching our content? If so, we kindly ask you to support us in producing high-quality & independent AWS content. We look forward to sharing our AWS knowledge with you.

Support us

Feedback? Questions? You can reach me via Email, Twitter, or LinkedIn.