Preliminary considerations
Names and tags are essential tools for effectively identifying, organizing and searching for Aruba Cloud services. Applying consistent naming and tagging rules is particularly useful in complex environments with multiple projects, users or teams.
Assigning a name to the service
- Choose a clear and descriptive name.
- If you use Aruba Cloud services in different environments, specify the environment in the name using prefixes or suffixes (for example, dev, test, prod, etc.).
- Avoid using names, nicknames, dates of birth or other sensitive information.
- Do not use generic names (for example, server1, db04, etc.).
Assigning tags to the service
- Define a standard to apply to all services.
- If you use Aruba Cloud services in different environments, specify the environment in the tags using prefixes or suffixes (for example, dev, test, prod, etc.).
- Use simple and straightforward tags: avoid overly complex tags or tags containing redundant information.
- Use short, easy-to-understand tags and avoid including too much information in a single tag.
- Avoid ambiguous tags: tags should be understandable by anyone, including users who did not create the service.