Tailwarden's Tag Management Policies provide a robust framework for ensuring consistent and effective tagging across your cloud infrastructure. These policies help maintain tagging consistency, enabling better resource management and cost allocation.
Purpose of Policies
The primary purpose of Tailwarden's Tag Management Policies is to ensure that all resources in your cloud environment adhere to a consistent tagging strategy. This consistency is crucial for efficient resource management, accurate cost allocation, and compliance with organizational standards.
A policy is composed of two elements:
The scope
Meaning on which resources this policy will be checked. It can be either
cloud accounts
one view (see this page to learn more about views)
The conditions on tags
You need to have at least one key
Values can be a specific list, or could be any values
How to Implement Policies
Step 1: Define name & scope
Step 2: Define conditions on tags
Step 3: Set-up notifications
As of today, notifications can be only received by slack. (please refer to this page to set-up slack on Tailwarden). Notifications through email will arrive soon.
Step 4: Enjoy
You will now find all the resources in the scope not matching the conditions on tags.
How to update or delete policies
You simply need to open the policy and open the submenu.
Example of policies you need to implement
Tag Owner for Roles:
Objective: Ensure clear ownership of roles.
Conditions: Any value or predefined list of individuals.
Tag Env for Every Resource:
Objective: Classify resources by environment.
Conditions: Values like "Sandbox," "Staging," or "Production."
Tag Cost Center for Billing Transparency:
Objective: Facilitate cost allocation and financial tracking.
Conditions: Cost center codes or identifiers.
Tag Compliance for Regulatory Requirements:
Objective: Ensure adherence to regulatory standards.
Conditions: Tags like "Compliant" or "Non-Compliant."
Tag Application for Microservices:
Objective: Categorize resources by serving application.
Conditions: Application names in a microservices architecture.
Tag Expiry Date for Temporary Resources:
Objective: Manage the lifecycle of temporary resources.
Conditions: Date values indicating resource expiration.
To learn more about policies and how to set-up your tag on autopilot to Tailwarden, here are additional resources:
Take back control of your tags with Tailwarden series
Ready to reclaim control of your cloud infrastructure? Connect with us to explore Tailwarden's capabilities and book a personalized demo.