⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Terraform & IaC Interview Questions Scenario 115 of 120 in Terraform & IaC
Senior DevOps / Platform Engineer Terraform Modules & Environment Configuration Operations & Support Loop

Q: How do you accommodate environment-specific variations, such as different EC2 instance sizes/types, across multiple environments in Terraform?

Architectural design for managing environment-specific configurations (such as different EC2 instance types and replica counts) across dev, staging, and production using clean Terraform patterns.

#Terraform #IaC #Multi-Environment #Terragrunt #Variables #Modules
🎙️ Candidate Opening & Architectural Context
"The biggest anti-pattern in infrastructure as code is copying and pasting duplicate Terraform directories for dev, staging, and prod. I maintain a single reusable module codebase and inject environment-specific variations using variable definition files (.tfvars), lookup maps, or Terragrunt orchestration."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: The biggest anti-pattern in infrastructure as code is copying and pasting duplicate Terraform directories for dev, staging, and prod. I maintain a single reusable module codebase and inject environment-specific variations using variable definition files (.tfvars), lookup maps, or Terragrunt orchestration.

1

Pattern 1: Environment-Specific .tfvars Files with Directory Isolation

Structure the repository with reusable modules, invoking them with dedicated backend state and variable files per environment: envs/dev/terraform.tfvars, envs/staging/terraform.tfvars, envs/prod/terraform.tfvars.

# envs/dev/terraform.tfvars
instance_type = "t3.medium"
min_replicas  = 2
max_replicas  = 4
enable_ha     = false

# envs/prod/terraform.tfvars
instance_type = "c6i.2xlarge"
min_replicas  = 10
max_replicas  = 50
enable_ha     = true
2

Pattern 2: Terraform Map Lookups Based on Environment Workspace/Variable

Define a structured map within the module using the environment name as the lookup key. This enforces centralized governance over permitted SKUs.

variable "environment" {
  type    = string
  default = "dev"
}

locals {
  instance_type_map = {
    dev     = "t3.medium"
    staging = "m5.large"
    prod    = "c6i.2xlarge"
  }
  instance_type = lookup(local.instance_type_map, var.environment, "t3.medium")
}
Advertisement
3

Pattern 3: DRY Orchestration with Terragrunt

Use Terragrunt to keep Terraform configurations 100% DRY. Define module sources once and pass environment-specific inputs via env.hcl files.

# terragrunt.hcl in /live/prod/compute
include "root" { path = find_in_parent_folders() }
terraform { source = "git::git@github.com:org/tf-modules.git//compute?ref=v2.1.0" }
inputs = {
  instance_type = "c6i.2xlarge"
  node_count    = 20
}
4

Validation & Guardrails via HCL Validation Blocks

Add Terraform variable validation blocks to prevent developers from provisioning expensive production instance types in development environments.

Pro Tip: Best Practice: Separate state files completely by account or folder (dev vs prod) to minimize blast radius while keeping module logic 100% shared.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Accommodate environment variations using shared reusable modules parameterized via environment-specific .tfvars files, local lookup maps, or Terragrunt. Isolate state files by environment to contain blast radius."
⚡ 60-Second Elevator Pitch Talking Points
  • Use a single reusable Terraform module referenced across all environments to avoid duplicate code.
  • Inject instance sizes and capacities via environment-specific .tfvars files or local lookup maps.
  • Adopt Terragrunt to manage multi-account inputs with zero code duplication.
  • Enforce variable validation rules to prevent oversized instances from being deployed in dev environments.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring Managing Environment Specific Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
  2. Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring Managing Environment Specific Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
  3. Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring Managing Environment Specific Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
  4. Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring Managing Environment Specific Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.
Advertisement
Want more Terraform & IaC scenarios?
Explore our complete collection of scenario-based Terraform & IaC interview runbooks.
Browse All Terraform & IaC Questions →