Check AWS billing tag coverage before allocating costs
On this page
Missing billing tags can mislead cost allocation, so check activation and historical coverage before treating absent export values as tagging failures. Review the exact resourceTags/ key in CUR 2.0, and do not treat line-item presence counts as spend coverage.
What you need first
- Tool
- Use the AWS Billing and Cost Management console, AWS's billing interface. Start at Cost allocation tags. For line-item review, use an existing AWS Cost and Usage Report (CUR) 2.0 export with the tags map selected.
- Access
- Ask an authorized billing colleague in the management account or a standalone account for the key's status. Ask an authorized data colleague for read-only tag-presence results for the agreed export scope and period.
- If you do not use that tool
- Give billing and data colleagues the resource-tag key, accounts, and reporting months. Request activation status, historical tag-assignment information, and line-item presence counts from the existing CUR 2.0 tags map.
Why this is worth a look
You can misclassify billing gaps as tagging failures if you skip activation and history checks. Activating a key affects every tag value that shares that key. In CUR 2.0, an enabled key appears in the tags map only when a value applies to that line item.
Backfill uses current activation status for past months. It cannot recover values from before a resource carried the tag, and it can remove currently inactive tags from historical cost data.
Run this check
CHECKLISTComplete this worksheet using Cost allocation tags in the billing console and an existing CUR 2.0 export, or ask authorized billing and data colleagues to return the results. Counts are line items, not spend or distinct resources. No settings are changed.
READ-ONLY REVIEW. Do not activate, deactivate, or request backfill.
Scope
[ ] Record the accounts covered: ____________________
[ ] Record the reporting start and end dates: ____________________
[ ] Identify the existing CUR 2.0 export: ____________________
[ ] Confirm that its tags map was selected. Stop if it was not.
Activation and history
[ ] Read the key's current status in Billing and Cost Management > Cost allocation tags, or obtain it from an authorized billing colleague.
Tag key: ____________________ Status: ____________________
[ ] Record when the tag was created and applied, and when activation was requested, if known. Mark unknown dates as unknown.
[ ] Record which requested months had the tag assigned to the resources. Mark unknown history as unresolved.
[ ] If reviewing a completed backfill, confirm the next daily data refresh has occurred before using its results.
Line-item presence
[ ] Confirm the exact key in the tags map. Example only: resourceTags/department.
Exact exported key: ____________________
[ ] Ask the authorized data colleague to count rows with that key present and rows with it absent, using only the recorded scope and period.
Present: __________ Absent: __________ Total reviewed: __________
[ ] Record whether present values are usable for allocation. Key presence alone does not validate a value.
[ ] Keep absent values unresolved until activation, historical assignment, and line-item applicability have been reviewed. Do not label these counts as spend coverage.
How to confirm it
- 01
Set the review scope
Record the accounts, reporting months, and existing CUR 2.0 export in the worksheet. Confirm that the tags map was selected before asking for counts. Use the exact resourceTags/ key, not an accountTag/ or costCategory/ key with the same name.
- 02
Read activation status
Check Billing and Cost Management > Cost allocation tags, or request the status from your billing colleague. Only management accounts and standalone accounts outside an organization can access this manager. Wait up to 24 hours after tag creation and application for a key to appear, then up to 24 more hours for activation.
- 03
Separate historical gaps
Confirm when resources first carried the tag. If backfill is being considered, review current activation status with the billing owner first: backfill can remove inactive tags from past data. Management account users can request up to 12 months of backfill, but values require historical resource assignment. For completed backfill, wait for the next daily data refresh.
- 04
Review presence without overstating coverage
Request the worksheet's counts from your data colleague for the recorded period and accounts. Review absent values against activation and tag history before proposing resource-tagging work. Keep the allocation decision open when history or line-item applicability remains unresolved.
Before making changes
Assumptions: this review uses an existing CUR 2.0 export with tags selected, an exact exported key, and results limited to the recorded accounts and dates. An absent line-item value is not proof of a tagging failure. Presence does not validate the value, and row counts do not measure spend or resource inventory. Cost allocation tag behavior varies across AWS services.