When creating a tagging strategy for AWS resources, make sure that it accurately represents organizationally relevant dimensions and adheres to the following tagging best practices:

• Select a Standardized Method for Tag Names.

  AWS tags are case-sensitive. Using a standardized, case-sensitive format for tags and performing it consistently across all resources is highly recommended. So, we tend to use all lowercase with hyphens for separators to avoid confusion about capitalizing a tag name.

• Start Small but Smart.

  A small set of tags that are known to be critical and needed is better than specifying an overabundance of tags that we predict to be required for the future. You can always create new tags as your need emerges.

• Implement automated tools (Tagging Governance)

  Every repetitive task is an opportunity for human error, and inserting tags by hand is no exception. Tags are not helpful if they carry missing or invalid data. Tag values should be set by automation. The automation code can be reviewed, tested, and enhanced to ensure that valid tag values are used.

• Use prefix for naming (Optional)

  Consider using a prefix identifying the team or organization. The prefix can show us that your team has named the tag, not by a third-party or AWS itself. For example, datamesh:application-id