What convention patterns are officially recommended or in common use for AWS services [closed]
Are there any officially recommended naming conventions and practices for AWS resources, or commonly applied patterns to be able to organise resources? What are some of the main considerations when structuring resources in AWS?
Naming standards are really up to you. What do you need to know about the resource? It will probably be different for each resource type. Some way to indicate application, owner, operating system or function, to distinguish between resources of that type.
Tagging is a superset of naming, and IMHO is more important than a naming convention. AWS has a PDF on tagging best practices, but here are tags I find most useful (from memory):
- Name: Displayed in console if you get the case correct (capital N), human readable description
- environment: development, testing, production, etc
- business-owner: who in the company is responsible for this - ideally a role based email rather than an individual
- technical-owner: the person who created or manages the resource
- description: optionally a description
- application-name: the name of the application the resource is associated with
- backups: when / what kind of backups are required (machine readable)
- schedule: when the resource needs to be turned on and off to save money (machine readable)