Cloud service providers (such as AWS, Azure, and GCP), allow us to add tags to cloud resources. These tags serve multiple functions.
This post gives a brief overview of what tags are and why we should use them when managing environments in the cloud.
Tags are metadata that we can add to a cloud resource (such as virtual machine, network interface, volume disk, etc.) for logical organization of resources.
Tags are text-based strings. Therefore, it is recommended to create them consistently across all cloud resources.
Why should you tag cloud resources?
- Cost allocation – Tagging enables us to differentiate between projects, departments, customers, etc. for billing reports
- Automation – Tagging enables us to put all relevant resources (compute, network, storage, etc.) in one place for the use of automation tools/scripts. For example, to turn off all resources with the same tag every night.
- Access control – Tagging enables us to control who has access to specific resources – for example who has privileges to see a dashboard of currently used resources in a specific project.
Cloud providers have been kind enough to create guidelines and tips for tagging. Here are just a few:
- How should I tag my AWS resources?
- Tagging Your Amazon EC2 Resources
- Use tags to organize your Azure resources
- Azure Resource Tagging Best Practices
- Best Practices for Enterprise Organizations
- Using labels to organize Google Cloud Platform resources
Eyal Estrin is a Cloud Architect.
He joined IUCC in December 2017 and his main focus is promoting and supporting cloud services in Universities in Israel. He brings with him more than 20 years of experience in the IT and information security field.
Follow him at @eyalestrin