Terraform Workspaces vs File Layout for Environment Isolation

#devops #terraform #beginners #tutorial

Day 7 focused on solving a real world problem in infrastructure management, handling multiple environments safely and efficiently.

In most projects, we need separate environments such as development, staging, and production. Terraform provides different ways to isolate these environments, and today I explored two of them.

Using Terraform Workspaces

Workspaces allow you to reuse the same configuration while maintaining separate state files for each environment.

I created three workspaces:

terraform workspace new dev

terraform workspace new staging

terraform workspace new production

Then I used the active workspace inside my configuration:

instance_type = var.instance_type[terraform.workspace]

This allowed me to dynamically change the instance type based on the environment.

Each workspace created its own infrastructure with separate state, even though the code was identical.

Using File Layout Isolation

The second approach was using separate directories for each environment.

environments/
dev/
staging/
production/

Each folder had its own Terraform configuration and backend pointing to a different state file in S3.

Example backend configuration:

backend "s3" {
bucket = "stephanie-day6-terraform-state-2026-unique"
key = "environments/dev/terraform.tfstate"
region = "us-east-1"
dynamodb_table = "terraform-state-locks"
encrypt = true
}

This ensured that each environment was completely isolated at both the code and state level.

Comparing the Two Approaches

Workspaces are simple and fast to use. They are ideal when you want to manage multiple environments using the same configuration with minimal setup.

However, they rely heavily on selecting the correct workspace. A mistake here can lead to changes being applied to the wrong environment.

File layout isolation is more structured. Each environment has its own directory and backend configuration, which reduces the risk of accidental changes. This approach is more suitable for production systems where safety is critical.

Key Takeaways

Workspaces provide quick and flexible environment separation
File layouts provide stronger isolation and clarity
Both approaches use separate state files to manage infrastructure
Choosing the right approach depends on project size and team needs

Final Thoughts

This lab showed that managing infrastructure is not just about creating resources. It is about organizing environments in a way that is safe, scalable, and easy to understand.

Understanding these patterns is essential for building reliable systems in real world DevOps workflows.