How to enable S3 bucket versioning using Terraform

This article is a part of my "100 data engineering tutorials in 100 days" challenge. (95/100)

S3 bucket versioning is like the trash function in operating systems. It saves the day when you accidentally remove something that should not be removed. It gets even better! Versioning allows you to restore the previous version when you overwrite a file that should not be overwritten.

In this article, I show you how to enable versioning of an S3 bucket using Terraform. Of course, keeping the old version and removed files costs money and, most likely, is unnecessary, so we should remove the old versions after some time. I will show you how to do it too!

We will need two things:

  • the name of the bucket
  • the number of days after which we want to remove the old versions

When we have all of that, we can define the bucket in Terraform configuration. In this example, I enable versioning of bucket called my_lovely_bucket. I want to remove the old versions after seven days:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
resource "aws_s3_bucket" "my_lovely_bucket" {
    bucket = "my_lovely_bucket"
    acl = "private"

    versioning {
        enabled = true
    }

    lifecycle_rule {
        enabled = true

        noncurrent_version_expiration {
            days = 7
        }
    }
}

Subscribe to the newsletter and join the free email course.


Remember to share on social media!
If you like this text, please share it on Facebook/Twitter/LinkedIn/Reddit or other social media.

If you want to contact me, send me a message on LinkedIn or Twitter.

Would you like to have a call and talk? Please schedule a meeting using this link.


Bartosz Mikulski
Bartosz Mikulski * MLOps Engineer / data engineer * conference speaker * co-founder of Software Craft Poznan & Poznan Scala User Group

Subscribe to the newsletter and get access to my free email course on building trustworthy data pipelines.