logo

Tagging best practices.
Identify tagging requirements.

It is extremely important to align all of the stakeholders, including technical and business units, to identify the exact tagging requirements of each group in order to deploy an effective tagging strategy that works for the entire organization.

Less is more

The simpler the approach to tagging, the easier it is to implement and maintain. Reducing redundant tags will simplify and streamline the implementation and maintenance of the tagging process. Start small and create new tags only when there is stakeholder consensus for the requirement.

Consistent use

Consistency is critical. Disregarding tagging standards will create complexity and consume time unnecessarily. A common example is missing or mislabeled cost allocation tags; if a large number of the deployed resources are affected, the cost analysis that leverages cost allocation tags could be grossly inaccurate.

A few additional guidelines and limitations to pay attention to:

- AWS tags are case sensitive and must be spelled correctly
- Each AWS tag should have a key that is less than 127 Unicode characters in UTF-8
- Each value assigned should be less than 255 Unicode characters in UTF-8
- AWS Tags are merely simple strings that you can assign a value to. Assigning a value does not create any semantic meaning for AWS
- The value assigned to a tag can be an empty string but it cannot be NULL
- You are limited to a maximum of 50 tags for most services
- You cannot use “AWS” as a prefix for the tag since it is reserved for AWS
- Characters that are acceptable for tags are letters, spaces, and numbers representable in UTF-8, along with the following special characters: + – = . _ : / @ .
- There are some AWS resources that can only be tagged using an API or CLI

AWS best practices

Only $19.99 Per Month

Tagging resources Dashboard AWS
© Tagbot 2020