How-to guide

Set up cost allocation tags on AWS

Learn how to pick a tag schema, tag AWS resources at scale, activate cost allocation tags, and verify cost reports by team or project.

By the Cloudverg engineering team · · 6 min read

Why this matters

Your AWS bill arrives at the account and service level. It does not know which team built the workload, which product pays for it, or whether it is production. Cost allocation tags add that context. Once a key is active, you can group and filter spend by it in AWS Cost Explorer, AWS Budgets and the Cost and Usage Report. Finance gets a map. Engineering gets an owner for a line item without guessing.

Tags do two jobs: showback and control. Showback gives each owner a saved view or budget filtered to their cost center. Control lets you see untagged spend before it becomes normal. A resource can carry tags that never appear in billing. The key has to be activated in Billing and Cost Management before it becomes a cost allocation tag.

Do not run this as a reporting side project. If the schema does not match how people approve spend and request changes, reports get ignored. Pick keys that map to budget owners and systems. A small set people use every month beats a large set that looks complete on paper.

Before you start

Decide who owns the tag dictionary first. Put finance and the platform group on it. One person approves new keys and values. Write a short page with key names, allowed values, owner, examples and the rule for shared resources. Keep it where engineers already look for build standards.

Check access. You need permission to open Billing and Cost Management, activate cost allocation tags, use Resource Groups Tag Editor and edit tag policies in AWS Organizations. If you use Organizations, activate cost allocation tags in the management account. Resources live in member accounts, but the payer account controls which keys become cost allocation tags in consolidated billing.

Know the tag rules. Tag keys are case sensitive, so CostCenter and costcenter are different. Stick to letters, numbers, spaces and the common symbols AWS allows. Not every AWS resource supports tags, and some services report charges without a resource that can carry your tag.

Start with four keys: CostCenter, Owner, Application and Environment. Add Project only if work is funded that way. Use a closed list for Environment, such as prod, stage, dev and sandbox. Put a team alias in Owner, not a person. Keep free text for a Notes tag you never activate for cost allocation.

How to do it

Roll out in two passes. First tag the resources that carry most of the bill and the ones people create by hand. Then add automation so new resources inherit the tags. Activate cost allocation tags after the first pass. If you activate before tags are in place, reports fill with blank values and people stop trusting them.

Use the console for a quick audit. Do bulk work in Resource Groups Tag Editor and in your infrastructure as code. A Terraform default_tags block, CloudFormation stack tags or CDK tag settings keep coverage steady. AWS Organizations tag policies help you find noncompliant tags, but they do not apply tags by themselves. If you need a hard gate, use service control policies with request tag conditions.

Activate a small set of keys first. Four to six active keys are enough for most teams. More keys make Cost Explorer grouping slow and reports harder to read. You can add keys later, but activation does not rewrite old billing history. The earlier you activate a key that is already on your resources, the more complete your trend line.

  1. Write the tag dictionary. List each key, its allowed values, the owner and one example. Keep the list short and put it in your engineering docs. Publish who can approve a new key.
  2. Tag the high-cost resources first. Open Cost Explorer and sort services by cost. Start with compute, storage and database resources that people create directly. Leave shared charges for a separate allocation rule.
  3. Use Tag Editor for bulk fixes. In Resource Groups, open Tag Editor, pick the regions and resource types, and search for resources with missing tags. Add or update tags in bulk and review the change list before you apply it. Tag Editor works across many services, but it cannot tag resources that do not support tags.
  4. Automate tags at create time. Add required tags in Terraform, CloudFormation, CDK or your launch templates. Make the pipeline fail when a required tag is missing. Test with a small stack before you enforce it everywhere.
  5. Activate cost allocation tags. In Billing and Cost Management, open Cost allocation tags. Select your user-defined keys and choose Activate. Give it a day, then check Cost Explorer for the new tag dimension.
  6. Add tag policies in AWS Organizations. Create a tag policy that defines the allowed values for CostCenter and Environment. Attach it to the accounts or OU that need it. Use the compliance view to find drift, not as a replacement for create-time tagging.
  7. Build saved views and budgets. In Cost Explorer, group by CostCenter and filter to production or a single application. Save the view and share it with the owner. Create an AWS Budget with the same tag filter and send alerts to the owner list.
  8. Review coverage every month. Look for the untagged group in each saved view. Find the resource, fix the tag and fix the automation that missed it. Update the dictionary when a new team or product appears.

How to check it worked

After activation, open AWS Cost Explorer and group by Tag. Pick CostCenter. You should see your allowed values, not a list of typos. Filter to one key and look for the blank or No tag group. That group is your coverage gap. New tag keys do not appear at once, so check the next day.

Open the Cost and Usage Report and add your cost allocation tag columns. Find a resource you tagged by hand and confirm the value appears on its usage line. Compare a sample in Tag Editor with the report. If the resource has the tag but the report does not, check activation, key case and whether the service reports that tag.

Test automation. Launch a small resource through your normal pipeline with the required tags. Wait for billing data and confirm it lands in the right cost center. Launch one without tags and confirm your budget or AWS Cost Anomaly Detection alert catches it. Check the tag policy compliance view too.

Open each owner's saved view and budget. Send a test notification to the owner list. A budget that filters on a tag with no data will look healthy while spend runs somewhere else. Put the view, the budget and the review date in one runbook.

Mistakes to avoid

A common failure is activating too many keys. It creates a wide report where every key has gaps. Start with keys people will use in a monthly review. Free text values cause the same problem. Prod, production and PROD become three groups in the report. Tag keys are case sensitive too.

Do not assume tag policies apply tags. They define and check values. A resource can be noncompliant and still cost money. Fix tags at create time in your infrastructure as code, then use Tag Editor for drift. Do not tag one region or one account and call it done. Autoscaling groups, managed services and new accounts create resources in places people forget.

Plan for untaggable and shared costs. AWS Support, some data transfer, taxes and some marketplace charges may not carry your tags. Write down how you split them and label the rule. Do not change a tag value and expect old costs to move. Cost allocation uses the tag at the time of usage, so history stays under the old value.

If you need a baseline before you commit to a schema, an outside review can help. The Cloud cost audit from Cloudverg is $4,500/month, a two week read-only review that includes tagging and budget alert fixes and a ranked savings report. It is one option next to an internal cleanup or a consultant you already use.

Frequently asked questions

Do cost allocation tags apply to past AWS costs?

No. Activation changes how future usage is reported, not the old bill. Resources that already carry the tag will start showing costs under that key from activation onward. Plan the tag rollout before you need clean history.

Where do I activate cost allocation tags in AWS?

In the Billing and Cost Management console, open Cost allocation tags. Select the user-defined keys you want and choose Activate. If you use AWS Organizations, do this in the management account so member account costs roll up.

What is the difference between a tag and a cost allocation tag?

A tag is metadata on a resource. A cost allocation tag is a tag key that AWS has activated for billing reports. The resource tag can exist for years and never appear in Cost Explorer until you activate the key.

Monthly plan

Want help with this? Cloud cost audit

$4,500/month

2 weeks · Starts within 10 business days

A two-week, read-only review of your AWS, Azure, Google Cloud or Oracle bill, with every saving ranked by dollars per month.

Renews monthly. Cancel any time.
What is included

Related guides

More cloud costs guides   Cloud cost audit

Smallest way to start

Get a senior architect on your problem this week

Ninety minutes a month on the cloud, AI or security question that is blocking you, a pre-read of your material and a written summary within two business days.

$450/month

Renews monthly. Cancel any time.