Pick a cloud to start. Your conventions autosave in this browser only, so back them up as a JSON file to keep them safe or continue on another device.
💾 Saving, backing up & picking up later
- Autosaved in this browser. Every change is saved instantly to this browser's local storage. Nothing is uploaded to our server.
- It can disappear. Clearing site data, private/incognito windows, a different browser or another computer won't have your conventions.
- Back up: Back up all downloads every convention (all clouds) as one JSON file. Export JSON saves just the current one. Keep the file with your team docs or in your repo.
- Pick up later: open the site on any device, choose Import JSON and select your backup. It's added alongside what's already there and checked against the latest provider rules.
- Share: Share link copies a URL that contains the convention. Opening it imports a copy for the other person, and your changes don't sync to them.
Convention
Loading rules…💾 Saving, backing up & picking up later
- Autosaved in this browser. Every change is saved instantly to this browser's local storage. Nothing is uploaded to our server.
- It can disappear. Clearing site data, private/incognito windows, a different browser or another computer won't have your conventions.
- Back up: Back up all downloads every convention (all clouds) as one JSON file. Export JSON saves just the current one. Keep the file with your team docs or in your repo.
- Pick up later: open the site on any device, choose Import JSON and select your backup. It's added alongside what's already there and checked against the latest provider rules.
- Share: Share link copies a URL that contains the convention. Opening it imports a copy for the other person, and your changes don't sync to them.
1 · Organization & pattern
3 · Resource abbreviations in this convention
| Resource | Abbr | Recommended | Example | Status |
|---|
No resource types yet — build a name above and click "Add", or add the most common ones.
Examples, Terraform and Bicep exports use the region, environment, workload and instance currently selected in step 2.
4 · Check existing names
| Name | Detected type | Result |
|---|
Detects the resource type from its abbreviation, then checks the provider's length and character rules plus your prefix, environment and region codes.
Cloud resource naming conventions, generated
What is a cloud resource naming convention?
A naming convention is an agreed pattern, such as {org}-{type}-{workload}-{env}-{region}-{instance}, that every team uses to name cloud resources. Consistent names make it obvious what a resource is, who owns it, which environment it belongs to and where it runs, which simplifies cost reporting, automation and incident response.
Which clouds does namingConventions.dev support?
Microsoft Azure (azure.namingconventions.dev), Amazon Web Services (aws.namingconventions.dev) and Google Cloud (google.namingconventions.dev). Each site uses that provider's own naming rules: length limits, allowed characters and recommended abbreviations.
Where are my conventions stored?
Only in your browser (localStorage). Nothing is uploaded. Use Export to download your convention as CSV, a Markdown guide or JSON, and Import to load it on another machine or share it with your team.
How does it stay up to date?
The server refreshes provider data daily. If a recommended abbreviation or naming rule changes after you saved a convention, the page flags it and lets you adopt the new recommendation or keep yours.
Microsoft Azure naming conventions · Amazon Web Services naming conventions · Google Cloud naming conventions