Terraform
- Terraform Enterprise
 - 1.0.x (latest)
 - v202507-1
 - v202506-1
 - v202505-1
 - v202504-1
 - v202503-1
 - v202502-2
 - v202502-1
 - v202501-1
 - v202411-2
 - v202411-1
 - v202410-1
 - v202409-3
 - v202409-2
 - v202409-1
 - No versions of this document exist before v202408-1. Click below to redirect to the version homepage.
 - v202408-1
 - v202407-1
 - v202406-1
 - v202405-1
 - v202404-2
 - v202404-1
 - v202402-2
 - v202402-1
 - v202401-2
 - v202401-1
 - v202312-1
 - v202311-1
 - v202310-1
 - v202309-1
 - v202308-1
 - v202307-1
 - v202306-1
 - v202305-2
 - v202305-1
 - v202304-1
 - v202303-1
 - v202302-1
 - v202301-2
 - v202301-1
 - v202212-2
 - v202212-1
 - v202211-1
 - v202210-1
 - v202209-2
 - v202209-1
 - v202208-3
 - v202208-2
 - v202208-1
 - v202207-1
 - v202206-1
 
Workspace Naming
Terraform Cloud organizes workspaces by name, so it's important to use a consistent and informative naming strategy. And although future releases of Terraform Cloud will add more organizational tools, the name will always be the most important piece of information about a workspace.
Workspace names need to be 90 characters or less and can only include letters, numbers, -, and _.
The best way to make names that are both unique and useful is to combine the workspace's most distinguishing attributes in a consistent order. Attributes can be any defining characteristic of a workspace — such as the component being managed, the environment it runs in, and the region it is provisioned into.
A good strategy to start with is <COMPONENT>-<ENVIRONMENT>-<REGION>. For example:
- networking-prod-us-east
 - networking-staging-us-east
 - networking-prod-eu-central
 - networking-staging-eu-central
 - monitoring-prod-us-east
 - monitoring-staging-us-east
 - monitoring-prod-eu-central
 - monitoring-staging-eu-central
 
If those three attributes can't uniquely distinguish all of your workspaces, you might need to add another attribute; for example, the infrastructure provider (AWS, GCP, Azure), datacenter, or line of business.