Lifecycle customization in Terraform - Mini Project: Build & Apply

Terraform Lifecycle Customization

📖 Scenario: You are managing cloud infrastructure using Terraform. Sometimes, you want to control how Terraform handles resource changes, like preventing deletion or ignoring certain attribute changes.

🎯 Goal: Build a Terraform configuration that creates an AWS S3 bucket with lifecycle customization to prevent accidental deletion and ignore changes to the bucket's tags.

📋 What You'll Learn

Create an AWS S3 bucket resource named my_bucket with the bucket name my-unique-bucket-12345

Add a lifecycle block to my_bucket that prevents the bucket from being deleted

Configure the lifecycle block to ignore changes to the tags attribute

💡 Why This Matters

🌍 Real World

Lifecycle customization in Terraform helps protect critical cloud resources from accidental deletion and manage updates safely.

💼 Career

Cloud engineers and DevOps professionals use lifecycle blocks to control resource behavior during infrastructure changes.

1

Create AWS S3 bucket resource

Create a Terraform resource block named aws_s3_bucket.my_bucket with the bucket name set to "my-unique-bucket-12345".

Terraform

# Your code here

Hint

Use resource "aws_s3_bucket" "my_bucket" {} and set the bucket attribute.

2

Add lifecycle block to prevent deletion

Inside the aws_s3_bucket.my_bucket resource, add a lifecycle block with prevent_destroy = true to stop accidental deletion.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-12345"
  # Add lifecycle block here
}

Hint

Use a lifecycle block with prevent_destroy = true inside the resource.

3

Configure lifecycle to ignore tag changes

Inside the lifecycle block of aws_s3_bucket.my_bucket, add ignore_changes = ["tags"] to ignore changes to the bucket's tags.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-12345"

  lifecycle {
    prevent_destroy = true
    # Add ignore_changes here
  }
}

Hint

Add ignore_changes = ["tags"] inside the lifecycle block.

4

Add tags to the S3 bucket

Add a tags attribute to aws_s3_bucket.my_bucket with Environment = "Dev" and Owner = "CloudTeam".

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-12345"

  lifecycle {
    prevent_destroy = true
    ignore_changes = ["tags"]
  }

  # Add tags here
}

Hint

Add a tags map with the specified keys and values inside the resource.

Practice

1. What does the create_before_destroy lifecycle setting do in Terraform?

easy

A. It ignores changes to specific resource attributes during updates.

B. It prevents the resource from being destroyed under any circumstances.

C. It forces Terraform to destroy the resource before creating a new one.

D. It creates a new resource before destroying the old one to avoid downtime.

Solution

1. Step 1: Understand the purpose of create_before_destroy

   This setting ensures Terraform creates the replacement resource first.

2. Step 2: Avoid downtime during resource replacement

   By creating the new resource before destroying the old, service interruptions are minimized.

3. Final Answer:

   It creates a new resource before destroying the old one to avoid downtime. -> Option D

4. Quick Check:

   create_before_destroy = create new before delete [OK]

Hint: Remember: create_before_destroy means new first, then old removed [OK]

Common Mistakes:

• Confusing create_before_destroy with prevent_destroy
• Thinking it deletes first then creates
• Assuming it ignores changes

2. Which of the following is the correct syntax to prevent a resource from being destroyed in Terraform?

easy

A. lifecycle { ignore_changes = true }

B. lifecycle { prevent_destroy = true }

C. lifecycle { create_before_destroy = true }

D. lifecycle { destroy_protection = true }

Solution

1. Step 1: Identify the correct lifecycle argument to prevent destruction

   The argument is prevent_destroy set to true.

2. Step 2: Verify syntax correctness

   The syntax is lifecycle { prevent_destroy = true }, which is valid Terraform code.

3. Final Answer:

   lifecycle { prevent_destroy = true } -> Option B

4. Quick Check:

   prevent_destroy = true prevents deletion [OK]

Hint: Use prevent_destroy = true to block resource deletion [OK]

Common Mistakes:

• Using ignore_changes instead of prevent_destroy
• Using a non-existent destroy_protection argument
• Confusing create_before_destroy with prevent_destroy

3. Given this Terraform resource snippet:

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"

  lifecycle {
    ignore_changes = ["tags"]
  }
}

What happens if you manually change the tags of this instance outside Terraform and then run terraform apply?

medium

A. Terraform will ignore the tag changes and keep the manual tags as is.

B. Terraform will destroy and recreate the instance to sync tags.

C. Terraform will throw an error due to tag mismatch.

D. Terraform will overwrite the manual tag changes with the configuration tags.

Solution

1. Step 1: Understand the effect of ignore_changes on tags

   The lifecycle setting ignore_changes = ["tags"] tells Terraform to ignore any changes to tags made outside Terraform.

2. Step 2: Predict Terraform behavior on apply

   Terraform will not attempt to update tags, so manual changes remain intact without error or replacement.

3. Final Answer:

   Terraform will ignore the tag changes and keep the manual tags as is. -> Option A

4. Quick Check:

   ignore_changes on tags means manual tag changes stay [OK]

Hint: ignore_changes = ["tags"] means Terraform skips tag updates [OK]

Common Mistakes:

• Assuming Terraform overwrites manual tag changes
• Expecting an error on tag mismatch
• Thinking resource will be recreated

4. You have this Terraform lifecycle block:

lifecycle {
  create_before_destroy = true
  prevent_destroy = true
}

What problem will occur if you try to update this resource that requires replacement?

medium

A. Terraform will create the new resource and destroy the old one successfully.

B. Terraform will ignore prevent_destroy and destroy the resource anyway.

C. Terraform will fail because it cannot destroy the old resource due to prevent_destroy.

D. Terraform will skip the update and keep the old resource unchanged.

Solution

1. Step 1: Analyze interaction of create_before_destroy and prevent_destroy

   create_before_destroy tries to create new resource before deleting old one, but prevent_destroy forbids deletion.

2. Step 2: Understand Terraform behavior on replacement

   Terraform cannot destroy the old resource due to prevent_destroy, so replacement fails.

3. Final Answer:

   Terraform will fail because it cannot destroy the old resource due to prevent_destroy. -> Option C

4. Quick Check:

   prevent_destroy blocks deletion, causing failure with create_before_destroy [OK]

Hint: prevent_destroy blocks deletion, so replacement fails [OK]

Common Mistakes:

• Assuming Terraform ignores prevent_destroy
• Thinking resource updates without replacement
• Believing create_before_destroy overrides prevent_destroy

5. You want to update an AWS S3 bucket's tags without triggering bucket replacement or downtime. Which lifecycle customization should you apply in Terraform to achieve this?

hard

A. Use ignore_changes = ["tags"] to skip tag updates.

B. Use prevent_destroy = true to block bucket deletion.

C. Use create_before_destroy = true to create new bucket first.

D. Use ignore_changes = ["versioning"] to skip versioning changes.

Solution

1. Step 1: Identify the goal to update tags without replacement

   Tags often cause resource updates; ignoring changes to tags avoids replacement.

2. Step 2: Choose lifecycle setting to ignore tag changes

   Setting ignore_changes = ["tags"] tells Terraform not to replace the bucket when tags change.

3. Final Answer:

   Use ignore_changes = ["tags"] to skip tag updates. -> Option A

4. Quick Check:

   ignore_changes on tags prevents replacement on tag updates [OK]

Hint: Ignore tag changes to update tags without replacement [OK]

Common Mistakes:

• Using prevent_destroy which blocks deletion but not replacement
• Using create_before_destroy which affects replacement order
• Ignoring unrelated attributes like versioning