Digital Labels
How do you know which team owns a specific virtual machine running in a massive data center somewhere? You can't look at it physically. The answer is tagging.
A tag is a simple piece of metadata — a label — that you attach to a cloud resource. It consists of a Key (the category) and a Value (the specific data for that resource). Think of it like a sticky note on a server.
| Key | Value |
|---|---|
Department |
Engineering |
Environment |
Staging |
Project |
WebsiteRedesign |
CostCenter |
4821 |
Why Tags Matter for Cost
When your cloud provider generates the bill, it includes these tags on every line item. This allows FinOps teams to group and filter costs based on any tag dimension. You can run a report that says: "Show me total spending for all resources tagged Department: Engineering." Without tags, this is impossible, and the bill remains a giant, unallocated mystery.
Tags are the raw material of every allocation, showback, and chargeback workflow. Every other FinOps practice in this topic depends on them being present, accurate, and consistent.
The Tag Coverage Problem
A common mistake is assuming that once you define a tagging policy, you have solved the problem. In reality, most organizations discover that 20–40% of their cloud spend is untagged or incorrectly tagged when they first audit their environment. This untagged spend is called dark spend — costs you cannot attribute to anyone. Reducing dark spend to below 5% is a meaningful FinOps milestone and often requires months of remediation work on legacy resources that predate any tagging policy.