A finance team applied a project tag to every S3 bucket and EBS volume in a standalone AWS account. A week later, Cost Explorer still offers no way to filter or group storage costs by that tag. What is the missing step?
Choose an answer to check it. Afterward, select any option to review its explanation.
Resource tags do not show up in billing tools on their own. A user-defined tag has to be activated as a cost allocation tag before Cost Explorer and the cost allocation report can use it, and it can take up to 24 hours to appear.
Storage Class Analysis can group objects by tag, which makes it sound relevant. It studies access patterns to guide lifecycle transitions; it does not feed tags into Cost Explorer, and it would not cover EBS volumes at all.
Consolidated billing combines bills and discounts across many accounts, which is a cost feature but solves a different problem. A standalone account can already activate cost allocation tags without joining an organization.
Budgets are useful for alerting on project spend, so they seem related. A budget does not make an inactive tag available as a dimension in Cost Explorer; the tag still has to be activated first.
id qadd20967a1