Introduction

At DataChef, we have a tagging strategy when working with AWS. Each company has its set of requirements and needs concerning resource organization and management. Teams in the organization also may want to use tagging for different purposes like automation, security, and access control.

Current Tagging Strategy

<aside> ⚠️ Do not use general or group email addresses for the Owner tag. Generic emails such as [email protected] are prohibited. Using personal company email addresses like **[email protected]**helps maintain clear accountability and facilitates direct communication.

</aside>

Currently, the only required tag is Owner*="<YOUR-EMAIL>"*. You can use this table to learn which tags you need to use when provisioning a new service. Adding all required tags to your services is necessary.

<aside> 🚨

We are currently transitioning to use the DLZ that requires PascalCase for Tag keys

</aside>

Considerations on tags’ keys and values

It is necessary to take a few considerations into account when we define a new tag or use predefined tags.

Use PascalCase for tag keys
Any value and format is permitted

Reserved Tags and Prefix

The following tags and prefixes should not be used or tagged in any of DataChef's AWS accounts. They are reserved by operations teams for defining automation or management.

Do not use aws: or AWS: prefix in your tag’s keys (reserved by AWS).
Do not use datachef: prefix in your tag’s keys or values. (we don’t currently use these but might)