CloudCostCompareTags and labels: how to see who spends what in the cloud
A cloud bill tells you what you spent on each service. It does not say which team, project or customer caused it. Tags, or labels, fill that gap: short key and value pairs you attach to resources, which then appear next to the cost.
The names differ, the idea does not
| Cloud | Name |
|---|---|
| AWS | Tags |
| Azure | Tags |
| Google Cloud | Labels |
| Oracle Cloud | Tags (free-form and defined) |
You choose the keys, for example team, project or environment, and set a value on each resource. Cost reports can then group by the key.
Things that catch people out
- Activation. On AWS, a tag shows in cost reports only after it is activated as a cost allocation tag in billing. Tagging resources is not enough.
- Not retroactive. A tag applies to charges from the time it is set, in most reports. Older charges stay unattributed.
- Not everything is taggable. Some charges, such as data transfer between services or support fees, do not carry a tag. A share of the bill will always be untagged.
- Inheritance varies. A tag on a resource group, folder or project does not always flow down to its resources. Check the vendor’s rule.
- Spelling counts.
Team,teamandteamsare different keys in many systems.
A scheme that works
Keep it small. Three to five keys that every resource must have:
projectorservice: what it is part of.teamorowner: who answers when it costs too much.environment: production, staging or development.cost-center: if your finance team uses one.
Write the allowed values in a short document, so people choose from a list instead of inventing them.
Enforce it
A scheme nobody follows is worth little. Use the cloud’s own policy features to require tags when a resource is created, or to report resources that lack them. Run a monthly check for untagged spend, and treat a rising untagged share as a problem to fix.
What you can do with it
- Show each team its own bill, which changes behavior more than any lecture.
- Find the owner of an unexpected cost within minutes.
- Set a budget per project. See budgets and cost alerts.
- Split shared costs fairly, once you can see usage.
For the larger picture of managing cloud spend as a habit, see FinOps basics for small teams. To check a tagged export against the bill, follow how to read a cloud bill.