Creation-time vs destruction-time in Terraform - Hands-On Comparison

Creation-time vs destruction-time in Terraform

📖 Scenario: You are managing cloud resources using Terraform. You want to understand how to set values that are fixed when resources are created (creation-time) versus values that can be changed or removed when resources are destroyed (destruction-time).

🎯 Goal: Build a Terraform configuration that defines a resource with a creation-time attribute and a destruction-time attribute, showing how to set and update these values properly.

📋 What You'll Learn

Create a Terraform resource with a fixed creation-time attribute

Add a variable to configure a destruction-time attribute

Use Terraform expressions to assign these attributes correctly

Complete the resource configuration with lifecycle rules

💡 Why This Matters

🌍 Real World

Managing cloud infrastructure with Terraform requires understanding which resource attributes can be changed without recreating resources and which cannot. This helps avoid downtime and data loss.

💼 Career

Cloud engineers and DevOps professionals must write Terraform code that safely manages resource lifecycle, balancing fixed creation-time settings with flexible destruction-time updates.

1

Define a Terraform resource with a creation-time attribute

Create a Terraform resource called aws_s3_bucket named example_bucket with the attribute bucket set to the fixed string my-fixed-bucket-name.

Terraform

# Your code here

Hint

The bucket name is fixed at creation time and cannot be changed later.

2

Add a variable for destruction-time attribute

Add a Terraform variable called enable_versioning of type bool with a default value false to control versioning on the bucket.

Terraform

resource "aws_s3_bucket" "example_bucket" {
  bucket = "my-fixed-bucket-name"
}

# Your code here

Hint

Variables allow you to configure attributes that can be changed without recreating the resource.

3

Use the variable to configure destruction-time attribute

Update the aws_s3_bucket.example_bucket resource to add a versioning block. Set enabled to the variable enable_versioning.

Terraform

variable "enable_versioning" {
  type    = bool
  default = false
}

resource "aws_s3_bucket" "example_bucket" {
  bucket = "my-fixed-bucket-name"
  # Your code here
}

Hint

The versioning block can be changed after creation, so it is a destruction-time attribute.

4

Add lifecycle rule to prevent bucket recreation

Add a lifecycle block inside aws_s3_bucket.example_bucket with prevent_destroy = true to avoid accidental bucket deletion.

Terraform

variable "enable_versioning" {
  type    = bool
  default = false
}

resource "aws_s3_bucket" "example_bucket" {
  bucket = "my-fixed-bucket-name"

  versioning {
    enabled = var.enable_versioning
  }

  # Your code here
}

Hint

This lifecycle rule protects the bucket from being destroyed accidentally.

Practice

1. What does creation-time mean in Terraform?

easy

A. The moment when resources are first set up or created

B. The moment when resources are deleted or removed

C. The time when Terraform runs a plan without changes

D. The time when Terraform refreshes the state

Solution

1. Step 1: Understand creation-time meaning

   Creation-time refers to when Terraform sets up resources for the first time.

2. Step 2: Differentiate from destruction-time

   Destruction-time is when resources are removed, not created.

3. Final Answer:

   The moment when resources are first set up or created -> Option A

4. Quick Check:

   Creation-time = resource setup [OK]

Hint: Creation-time means resource setup, destruction-time means removal [OK]

Common Mistakes:

• Confusing creation-time with destruction-time
• Thinking creation-time is when resources are deleted
• Mixing creation-time with Terraform plan execution

2. Which Terraform lifecycle argument controls actions at destruction-time?

easy

A. create_before_destroy

B. depends_on

C. ignore_changes

D. prevent_destroy

Solution

1. Step 1: Identify destruction-time control arguments

   The prevent_destroy argument stops Terraform from deleting a resource.

2. Step 2: Compare other lifecycle arguments

   create_before_destroy affects creation and replacement order, not destruction prevention.

3. Final Answer:

   prevent_destroy -> Option D

4. Quick Check:

   Destruction-time control = prevent_destroy [OK]

Hint: Use prevent_destroy to block resource deletion at destruction-time [OK]

Common Mistakes:

• Choosing create_before_destroy which affects creation order
• Confusing ignore_changes with destruction control
• Using depends_on which manages resource dependencies

3. Given this Terraform snippet:

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

  lifecycle {
    create_before_destroy = true
  }
}

What happens when you change instance_type from t2.micro to t2.small?

medium

A. Terraform destroys the old instance first, then creates the new one

B. Terraform updates the instance in place without destruction

C. Terraform creates the new instance first, then destroys the old one

D. Terraform throws an error due to lifecycle conflict

Solution

1. Step 1: Understand create_before_destroy effect

   This setting makes Terraform create the new resource before destroying the old one.

2. Step 2: Apply to instance_type change

   Changing instance_type forces replacement, so new instance is created first, then old destroyed.

3. Final Answer:

   Terraform creates the new instance first, then destroys the old one -> Option C

4. Quick Check:

   create_before_destroy = new before old [OK]

Hint: create_before_destroy means new resource before old is removed [OK]

Common Mistakes:

• Assuming in-place update without replacement
• Thinking old resource is destroyed before new is created
• Believing lifecycle causes errors on changes

4. You added prevent_destroy = true to a resource but Terraform still deletes it on terraform destroy. What is the likely cause?

medium

A. You ran terraform destroy which ignores prevent_destroy

B. The prevent_destroy argument is misspelled or misplaced

C. The resource is referenced by another resource with depends_on

D. Terraform does not support prevent_destroy for that resource type

Solution

1. Step 1: Check prevent_destroy usage

   It must be inside the lifecycle block and spelled correctly.

2. Step 2: Understand terraform destroy behavior

   terraform destroy respects prevent_destroy and will error if deletion is blocked.

3. Final Answer:

   The prevent_destroy argument is misspelled or misplaced -> Option B

4. Quick Check:

   Misplaced prevent_destroy causes deletion despite protection [OK]

Hint: Ensure prevent_destroy is inside lifecycle block and spelled right [OK]

Common Mistakes:

• Assuming terraform destroy ignores prevent_destroy
• Placing prevent_destroy outside lifecycle block
• Thinking depends_on affects prevent_destroy behavior

5. You want to replace a resource safely without downtime. Which lifecycle settings should you use to ensure the new resource is created before the old one is destroyed, and prevent accidental deletion?

hard

A. Set create_before_destroy = true and prevent_destroy = true

B. Set create_before_destroy = false and prevent_destroy = true

C. Set create_before_destroy = true and ignore_changes = [all]

D. Set prevent_destroy = false and ignore_changes = [all]

Solution

1. Step 1: Use create_before_destroy for safe replacement

   This ensures the new resource is ready before the old one is removed, avoiding downtime.

2. Step 2: Use prevent_destroy to block accidental deletion

   This stops Terraform from deleting the resource unless explicitly allowed, adding safety.

3. Final Answer:

   Set create_before_destroy = true and prevent_destroy = true -> Option A

4. Quick Check:

   Safe replacement = create_before_destroy + prevent_destroy [OK]

Hint: Combine create_before_destroy and prevent_destroy for safe updates [OK]

Common Mistakes:

• Setting prevent_destroy without create_before_destroy causes downtime
• Using ignore_changes to avoid destruction which doesn't prevent deletion
• Disabling prevent_destroy risks accidental resource loss