Here are some lesser-known Terraform tricks that can level up your infrastructure automation game.

1️⃣ depends_on in Modules: The Right Way to Manage Dependencies

🔹 Problem: Terraform does not allow implicit dependencies inside modules. You might have faced situations where resources inside a module should wait for resources outside but don’t.
🔹 Solution: Use depends_on inside modules at the resource level instead of the module level.

🔍 Example:
Let’s say you are deploying an EC2 instance that depends on a Security Group from another module.

❌ Wrong approach (doesn’t work inside modules):

hclCopy codemodule "ec2" {
  source = "./modules/ec2"
  depends_on = [module.security_group]  # This won't work!
}

✅ Right approach:

hCopy coderesource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t3.micro"
  security_groups = [module.security_group.id]

  depends_on = [module.security_group]  # Works inside resource block
}

📌 Why? depends_on works inside resource blocks, not at the module level.

2️⃣ Using Terraform Functions for Dynamic Configurations

Many Terraform users hardcode values in .tf files, but Terraform has powerful built-in functions to generate values dynamically.

🔹 Example 1: Using cidrsubnet() to Dynamically Allocate Subnets

Instead of manually defining subnet CIDRs, use cidrsubnet() to dynamically split networks.

hclCopy codevariable "vpc_cidr" {
  default = "10.0.0.0/16"
}

resource "aws_subnet" "subnet1" {
  vpc_id     = aws_vpc.main.id
  cidr_block = cidrsubnet(var.vpc_cidr, 8, 1)  # Generates 10.0.1.0/24
}

📌 Why? This helps automate subnet creation without manually calculating CIDRs.

3️⃣ Preventing Costly Mistakes with lifecycle Rules

Terraform does not protect resources from accidental deletions or updates by default. You can prevent this with lifecycle policies.

🔹 Example: Prevent Deletion of an S3 Bucket

hclCopy coderesource "aws_s3_bucket" "example" {
  bucket = "my-secure-bucket"

  lifecycle {
    prevent_destroy = true  # Stops accidental deletion
  }
}

📌 Why? This prevents Terraform from destroying the bucket during terraform destroy.

🔸 Bonus Tip: Use ignore_changes = for fields that might change externally, such as manually modified IAM roles:

hclCopy codelifecycle {
  ignore_changes = [policy]
}

4️⃣ Generate Dynamic Resource Names with random_pet

Avoid hardcoding names by using Terraform’s random_pet resource to generate unique, readable names.

hclCopy coderesource "random_pet" "bucket_suffix" {}

resource "aws_s3_bucket" "example" {
  bucket = "my-bucket-${random_pet.bucket_suffix.id}"
}

📌 Why? This helps avoid naming conflicts without adding random UUIDs.

5️⃣ Locking Terraform State with AWS DynamoDB

🔹 Problem: Running terraform apply from multiple locations can lead to state corruption.
🔹 Solution: Use DynamoDB state locking to prevent concurrent state modifications.

🔹 Steps to Enable Remote State Locking

1️⃣ Create a DynamoDB table:

hclCopy coderesource "aws_dynamodb_table" "terraform_locks" {
  name         = "terraform-locks"
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "LockID"

  attribute {
    name = "LockID"
    type = "S"
  }
}

2️⃣ Configure Terraform backend with locking:

hclCopy codeterraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "state/terraform.tfstate"
    region         = "us-east-1"
    dynamodb_table = "terraform-locks"  # Enables locking
  }
}

📌 Why? This prevents race conditions in Terraform state, avoiding corruption.

6️⃣ Terraform output for Debugging and Automation

Instead of manually checking Terraform values, use output variables to print or pass data.

hclCopy codeoutput "instance_ip" {
  value = aws_instance.example.public_ip
}

📌 Why? This helps debug values or pass them to external scripts.

🔸 Bonus: Save output as JSON for automation:

shCopy codeterraform output -json > outputs.json

Final Thoughts 💡

Terraform is much more than just terraform apply. By using these advanced tricks, you can:
✅ Optimize resource management
✅ Improve security & avoid accidental changes
✅ Automate infrastructure more efficiently
✅ Debug Terraform more effectively

💬 Which trick did you find the most useful? Let me know in the comments! 🚀