Cloud cost
Cost allocation tags
Key-value labels applied to cloud resources so spend can be grouped by team, project, environment, or customer instead of showing up as one undifferentiated total.
Last updated
Definition
Without tags, a bill is just a flat total per service. There's no way to answer "how much did the checkout team's infrastructure cost last month" without manually cross-referencing resource names. Tags applied consistently at creation time (team, project, environment, and, for usage-based products, customer) let every downstream report slice spend along the lines the business cares about.
The practical failure mode is inconsistency: tags applied by convention rather than enforcement drift within a quarter, as new resources get created without them. Enforcing required tags at provisioning time (or a tag-compliance sweep) is what keeps allocation reporting trustworthy.
Where it shows up
Cost allocation tags are key-value pairs attached to a resource at creation, visible on the resource itself and, once activated in the billing console, as their own dimension for grouping and filtering spend by team, project, environment, or customer across the whole account, in every downstream report.
What makes it expensive
Teams get burned by applying tags by convention instead of enforcement, letting them drift as new resources get created without them. Nobody decides to stop tagging. Coverage measured in dollars simply slips a few points a quarter, with no policy change anywhere to explain it, until the allocation report stops being worth showing anyone.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
A total nobody owns, nobody fixes.
An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.