Platforms such as AWS, Google Cloud, and Azure offer many services and features to help you better control your Cloud environment. As an IT professional, it is important to adopt tagging within your company’s Cloud infrastructure.
Let’s first define the notion of tags and then understand why and how to apply them within your Cloud environment.
A tag is simply a label that you assign to a resource or a group of resources. The label is represented in the form of a key-value pair and will make it possible to add an attribute to a resource in order to categorize it. This becomes particularly important when it comes to sorting your resources according to certain common criteria. For example:
Thus, this practice will make it possible to coordinate resources and thus optimize the organization of these in your Cloud platform.
Before setting up tags on your various resources, it is important to define a tagging policy and apply certain best practices for logical and productive management of your Cloud environment. In fact, the larger your infrastructure, the more careful your organization needs to be.
First, it will be a question of defining a tag policy by setting up your naming convention such as spelling or even prefixing. Secondly, it will be good to integrate global tags such as:
|Type de tag||Examples||Fonction|
|Environnement||env:dev | env:test | env:prod||Identify the type of environment|
|Billing||region:us | owner:umaknow||Estimate the cost of the resources|
|Application||app:carapp | service:azure||Define the applications or services|
|Compliance||datalocation:australia | compliance:gdpr||Define compliance rules|
|Optimization||schedule:24/7||Automate actions on certain resources|
Following the implementation of global tags, you can quickly introduce more detailed tags according to your personal preferences or internal specificities of your company or team.
Depending on the platform you use, the tag naming constraints differ according to their respective documentation:
|Platform||No. of tags per resource||Tag key length||Tag value length||Case sensitivity||Restrictions/accepted characters|
|AWS||50||128||256||Yes||Prefix « aws: » is reserved | Letters, numbers, spaces and: + - = . _ : / @ are accepted|
|Azure||50||512||256||No||Not accepted: <, >, %, &, \, ?, /|
|GCP||64||63||63||Yes||Lowercase, numbers, underscore and dashes are accepted|
Note: if you use more than one of these platforms (multi-cloud architecture, or hybrid cloud architecture) it is advisable to assign key-values of 63 characters and write them in lowercase, with numbers, letters, and underscores.
Warning: if you use a similar tag from one platform to another, be sure to respect its value and its letter case for better management of resources across the board.
In order to make the tags applicable to all members of your organization, there are two ways of doing so in Azure, Google Cloud, and AWS. They are fully described in their respective documentation which you will find at the end of the article. You will then have the choice between:
For visualization and management of your tags, Cloudockit allows you to generate your Cloud documentation as well as your Cloud architecture diagrams by including the tags you will have assigned to your various resources in order to draw even more relevant information.
Now, through the use of tags, following best practices coupled with the use of Cloudockit, take full control of your Cloud infrastructure and get the most out of it.