Cloud service providers allow users to assign metadata to their cloud resources in the form of tags. Each tag is a simple label consisting of a customer-defined key and a value that can make it easier to manage, search for, and filter resources. Although there are no inherent types of tags, they enable customers to categorize resources by purpose, owner, environment, or other criteria.
Tags can be used for security, cost allocation, automation, console organization, access control, and operations.
On this show, we will review a new way to automate tags attribution in your CI/CD pipeline and AWS. We will also take a look at a new open-source tool to help us implement tagging best practices.
14. Tagging best practices
1. Employ a Cross-Functional Team to Identify Tag Requirements
2. Use Tags Consistently
3. Assign Owners to Define Tag Value Propositions
4. Focus on Required and Conditionally Required Tags
5. Start Small; Less is More
6. Use Automation to Proactively Tag Resources
7. Remediate Untagged Resources
16. What is
?
Open source (Apache 2.0) tagging
framework for IaC, intended to be used
in CI/CD pipelines
1. Automated tagging
2. Built in best practices for tracing
3. Built in best practices for ownership
18. What is Yor Trace?
Where did this
resource come from?
How was it
configured?
Where do I fix a
misconfig?
What runtime
resources are
provisioned from this
code?
No need to access state or sensitive
information to answer those questions
