Q: What is a Terraform workspace and what are its limitations?
Workspaces let you maintain multiple state files for the same configuration. terraform workspace new staging creates a staging workspace with its own state.
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: "Managing infrastructure as code across multiple teams requires disciplined state management and locking. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Workspaces let you maintain multiple state files for the same configuration. terraform workspace new staging creates a staging workspace with its own state.
- All workspaces use the same code — config differences between environments are hard (you'd use
terraform.workspacevariable conditionals, which gets messy). - Same backend — all workspace state files are in the same S3 bucket, just different keys.
- No access control — you can't restrict who applies to production workspace vs dev workspace.
Remediation & Permanent Safeguards
Limitations: Use workspaces for: small teams, temporary environments, exactly-same-config use cases. Don't use workspaces for: production vs staging (different configs, different access controls).
- Better alternative for multiple environments: separate directories/modules, not workspaces.
- All workspaces use the same code — config differences between environments are hard (you'd use te...
- Same backend — all workspace state files are in the same S3 bucket, just different keys.
- No access control — you can't restrict who applies to production workspace vs dev workspace.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring Terraform workspace limitations AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
-
Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring Terraform workspace limitations
Accessing SSE-KMS encrypted objects requires both
s3:GetObjectandkms:Decryptpermissions; neglecting KMS key policies causes silent 403 Forbidden errors. - Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring Terraform workspace limitations Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
- Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring Terraform workspace limitations Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.