When naming AWS resources, including instances, volumes, snapshots, and other resources, it’s important to follow a consistent naming convention that helps with organization, identification, and management. Here are some general guidelines for creating AWS resource names:
- Be descriptive: Use names that clearly indicate the purpose, function, or characteristics of the resource. This helps in understanding and identifying the resource later on.
- Use lowercase letters and hyphens: Stick to lowercase letters and use hyphens (“-“) to separate words within the name. Avoid using underscores or special characters.
- Keep it concise: Aim for brevity while maintaining clarity. Long and complex names can be difficult to manage and work with.
- Include relevant details: Incorporate relevant information such as environment (dev, prod), project, application, component, or department in the resource name if it helps differentiate and categorize resources.
- Use consistent conventions: Establish a consistent naming convention across your organization to facilitate easier management and understanding of resources.
- Avoid including sensitive information: Do not include sensitive data like passwords, credentials, or personally identifiable information in resource names.
Here’s an example of a naming convention for an EC2 instance:
[Environment]-[Application/Component]-[Role/Function]-[Number]
For example: prod-webserver-app-01
This convention includes the environment (prod), the application or component (webserver), the role or function (app), and a number (01) to differentiate multiple instances with similar characteristics.
Remember, the most important aspect is consistency. Choose a convention that works for your organization and ensures clear identification and management of resources.