Cost allocation tags are resource tags that have been switched on for billing, so AWS can break your bill down by them. A tag such as CostCentre = finance only shows up in cost reports once its key is activated as a cost allocation tag.

Tagging a resource and activating the tag for billing are two separate steps. Until the second step is done, the tag exists on the resource but your bill ignores it.

The two kinds

TypeWho creates itExample
User-definedYou, on your own resourcesOwner, Environment, Application, CostCentre
AWS-generatedAWS, automaticallyaws:createdBy: who created a resource

How to switch them on

In the Billing and Cost Management console, choose Cost allocation tags, select the tag keys and choose Activate (or use the UpdateCostAllocationTagsStatus API to do it in bulk). According to AWS's documentation, a new tag key can take up to 24 hours to appear on that page, and up to another 24 hours to activate. Activation applies to every value of that key.

Activation normally works forwards only, but the management account can request a backfill that applies the tag to up to 12 months of past cost data, as long as the tag was already on the resources at the time.

Once active, the tag becomes a filter and a "group by" option in Cost Explorer, AWS Budgets and the Cost and Usage Report.

What they won't do

  • They can't tag what isn't taggable. Support charges and some shared or data-transfer costs don't carry tags, so expect an "untagged" bucket.
  • They don't fix bad tags. prod, Prod and production are three different values in the bill. Consistency comes from a tagging standard and, in multi-account setups, tag policies.
  • They only see tagged resources. An untagged resource stays invisible in a tag-grouped view, which is often where the forgotten spend hides.

For a starter taxonomy and how to roll it out, see Tagging Strategy 101. Working out who owns each cost line is the first step of a Yemberzal Cost Optimisation Audit.