Loading page
About this tool
Generate a consistent Terraform resource naming standard across environments and regions, validated against real cloud name limits.
This generator produces a consistent Terraform resource naming standard of the form {org}-{app}-{env}-{region}-{type} and validates every generated name against real platform limits, such as the 63-character S3 bucket rule and the 24-character lowercase-only Azure storage account rule. It is built for platform and DevOps engineers who want one naming convention that works across AWS, Azure and Google Cloud without hitting provider errors at apply time.
Open Terraform Naming Convention Generator on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
Every name is checked against documented rules: S3 3-63 chars, Lambda and IAM 64, Azure storage 24, Key Vault 24, GCS 63.
Automatically strips hyphens or underscores where a platform forbids them, like underscores in S3 buckets.
Outputs a Terraform locals block with a name_prefix you can interpolate in every resource.
A widely used pattern is {org}-{app}-{env}-{region}-{type}, for example acme-billing-prod-use1-s3. Keeping tokens short, lowercase and in a fixed order makes names sortable in cloud consoles and lets you derive them from a single name_prefix local in Terraform.
Between 3 and 63 characters. S3 bucket names must use only lowercase letters, numbers, hyphens and dots, cannot look like an IP address, and are globally unique across all AWS accounts, so a short org token or account-id suffix helps avoid collisions.
Azure storage account names allow only lowercase letters and numbers, 3 to 24 characters, with no hyphens or underscores. A convention that works for resource groups will usually be too long or contain separators, which is why this tool strips separators and re-checks the length for storage accounts specifically.
Underscores. The HCL style convention is lowercase_with_underscores for resource labels (the name in code), while the cloud-facing name argument typically uses hyphens. The two are independent, and this tool generates both forms.