When to Use Workspaces in Terraform: Simple Guide

Use Terraform workspaces when you want to manage multiple distinct environments (like development, staging, production) using the same configuration. Workspaces keep separate state files, letting you switch contexts easily without duplicating code.

How It Works

Think of Terraform workspaces like different folders in a filing cabinet. Each folder holds its own set of documents (state files) that describe your infrastructure. When you switch folders, you see only the documents inside that folder, keeping things organized and separate.

This means you can use one set of Terraform code to create multiple environments. Each workspace keeps track of its own resources, so changes in one workspace don’t affect the others. It’s like having separate notebooks for different projects but using the same pen and paper style.

Example

This example shows how to create and switch between workspaces, then apply infrastructure changes separately.

bash

terraform workspace new dev
terraform workspace select dev
terraform apply -auto-approve

terraform workspace new prod
terraform workspace select prod
terraform apply -auto-approve

Output

Created and switched to workspace "dev".
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Created and switched to workspace "prod".
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

When to Use

Use workspaces when you want to manage multiple environments with the same Terraform code but keep their states separate. For example:

• Development, staging, and production environments
• Testing different versions of infrastructure safely
• Managing multiple clients or projects with similar setups

Workspaces help avoid copying code or creating separate folders for each environment, making your workflow cleaner and easier to maintain.

Key Points

• Workspaces isolate state files for different environments.
• They let you reuse the same Terraform code safely.
• Switching workspaces changes which environment you manage.
• Not ideal for very different infrastructure setups.
• Good for simple environment separation and testing.

Key Takeaways

Terraform workspaces separate state files to manage multiple environments with one codebase.

Use workspaces to switch easily between development, staging, and production setups.

Workspaces keep environments isolated but share the same configuration files.

Ideal for similar infrastructure environments, not for completely different setups.

Workspaces simplify managing multiple environments without code duplication.