Overview
To monitor cloud costs effectively, you need a complete and detailed view of how different services, teams, and products contribute to your overall spend. Tag Pipelines ensure your cloud resources use standard tags that you can leverage across the product so that no resource’s cost data slips through the cracks.
Create tag rules with tag pipelines to fix missing or incorrect tags on your Cloud bill, or to create new, inferred tags that align with business logic.
Rule types
A maximum of 100 rules can be created, and API based Reference Tables are not supported.
There are three types of rules supported: Add tag, Alias tag keys, and Map multiple tags. You can keep your rules organized by leveraging rules sets, which act as folders for your rules. The rules are executed in deterministic order (from top to bottom). You can organize rules and rule sets to ensure the order of execution matches your business logic.
Add tag
Add a new tag (key + value) based on the presence of existing tags on Cloud Costs data.
For example, you can create a rule to tag all resources with their business unit based on the services those resources are a part of.
Alias tag keys
Map existing tag values to a more standardized tag.
For example, if your organization wants to use the standard application tag key, but several teams have a variation of that tag (like app, webapp, or apps), you can alias apps to application. Each alias tag rule allows you to alias a maximum of 25 tag keys to a new tag.
The rule stops executing for each resource after a first match is found. For example, if a resource already has a app tag, then the rule no longer attempts to identify a webapp or apps tag.
Use Reference Tables to add multiple tags to cost data without creating multiple rules. This will map the values from your Reference Table’s primary key column to values from cost tags. If found, the pipelines adds the selected Reference Table columns as tags to cost data.
For example, if you want to add information about which VPs, organizations, and business_units different AWS and Azure accounts fall under, you can create a table and map the tags. Similar to Alias tag keys, the rule stops executing for each resource after a first match is found. For example, if an aws_member_account_id is found, then the rule no longer attempts to find a subscriptionid.
Further reading
Additional helpful documentation, links, and articles:
