DEV Community

Cover image for 28.Enable S3 Versioning Using Terraform
Thu Kha Kyawe
Thu Kha Kyawe

Posted on

28.Enable S3 Versioning Using Terraform

Lab Information

Data protection and recovery are fundamental aspects of data management. It's essential to have systems in place to ensure that data can be recovered in case of accidental deletion or corruption. The DevOps team has received a requirement for implementing such measures for one of the S3 buckets they are managing.

The S3 bucket name is datacenter-s3-9431, enable versioning for this bucket using Terraform.

The Terraform working directory is /home/bob/terraform. Update the main.tf file (do not create a different .tf file) to accomplish this task.

Note: Right-click under the EXPLORER section in VS Code and select Open in Integrated Terminal to launch the terminal.

Lab Solutions

Step 1: Create Main Terraform Configuration

# main.tf

resource "aws_s3_bucket" "s3_ran_bucket" {
  bucket = "datacenter-s3-9431"
  acl    = "private"

  tags = {
    Name        = "datacenter-s3-9431"
  }
}

# Enable versioning for the S3 bucket
resource "aws_s3_bucket_versioning" "s3_ran_bucket_versioning" {
  bucket = aws_s3_bucket.s3_ran_bucket.id

  versioning_configuration {
    status = "Enabled"
  }
}

Enter fullscreen mode Exit fullscreen mode

Step2: To deploy this configuration

Navigate to the Terraform directory:

cd /home/bob/terraform
Enter fullscreen mode Exit fullscreen mode

Initialize Terraform:

terraform init
Enter fullscreen mode Exit fullscreen mode

Output

bob@iac-server ~/terraform via πŸ’  default ➜  terraform init
Initializing the backend...
Initializing provider plugins...
- Finding hashicorp/aws versions matching "5.91.0"...
- Installing hashicorp/aws v5.91.0...
- Installed hashicorp/aws v5.91.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Enter fullscreen mode Exit fullscreen mode

Plan the deployment to verify the configuration:

terraform plan
Enter fullscreen mode Exit fullscreen mode

Output

bob@iac-server ~/terraform via πŸ’  default ➜  terraform plan
aws_s3_bucket.s3_ran_bucket: Refreshing state... [id=datacenter-s3-9431]

Terraform used the selected providers to generate the following execution plan. Resource
actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_s3_bucket_versioning.s3_ran_bucket_versioning will be created
  + resource "aws_s3_bucket_versioning" "s3_ran_bucket_versioning" {
      + bucket = "datacenter-s3-9431"
      + id     = (known after apply)

      + versioning_configuration {
          + mfa_delete = (known after apply)
          + status     = "Enabled"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
β•·
β”‚ Warning: Argument is deprecated
β”‚ 
β”‚   with aws_s3_bucket.s3_ran_bucket,
β”‚   on main.tf line 3, in resource "aws_s3_bucket" "s3_ran_bucket":
β”‚    3:   acl    = "private"
β”‚ 
β”‚ acl is deprecated. Use the aws_s3_bucket_acl resource instead.
β”‚ 
β”‚ (and one more similar warning elsewhere)
β•΅

─────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to
take exactly these actions if you run "terraform apply" now.
Enter fullscreen mode Exit fullscreen mode

Apply the configuration:

terraform apply
Enter fullscreen mode Exit fullscreen mode

Then type yes when prompted to confirm the creation of the snapshot.

Output

bob@iac-server ~/terraform via πŸ’  default ➜  terraform apply
aws_s3_bucket.s3_ran_bucket: Refreshing state... [id=datacenter-s3-9431]

Terraform used the selected providers to generate the following execution plan. Resource
actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_s3_bucket_versioning.s3_ran_bucket_versioning will be created
  + resource "aws_s3_bucket_versioning" "s3_ran_bucket_versioning" {
      + bucket = "datacenter-s3-9431"
      + id     = (known after apply)

      + versioning_configuration {
          + mfa_delete = (known after apply)
          + status     = "Enabled"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
β•·
β”‚ Warning: Argument is deprecated
β”‚ 
β”‚   with aws_s3_bucket.s3_ran_bucket,
β”‚   on main.tf line 3, in resource "aws_s3_bucket" "s3_ran_bucket":
β”‚    3:   acl    = "private"
β”‚ 
β”‚ acl is deprecated. Use the aws_s3_bucket_acl resource instead.
β”‚ 
β”‚ (and one more similar warning elsewhere)
β•΅

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_s3_bucket_versioning.s3_ran_bucket_versioning: Creating...
aws_s3_bucket_versioning.s3_ran_bucket_versioning: Creation complete after 2s [id=datacenter-s3-9431]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Enter fullscreen mode Exit fullscreen mode

Resources & Next Steps
πŸ“¦ Full Code Repository: KodeKloud Learning Labs
πŸ“– More Deep Dives: Whispering Cloud Insights - Read other technical articles
πŸ’¬ Join Discussion: DEV Community - Share your thoughts and questions
πŸ’Ό Let's Connect: LinkedIn - I'd love to connect with you

Credits
β€’ All labs are from: KodeKloud
β€’ I sincerely appreciate your provision of these valuable resources.

Top comments (0)