What is the MOST likely reason that the Business-Unit tag is absent?

By:
In: SOA-C01
Tagged:
With: 1 Comment
A company wants to track Amazon EC2 usage charges that are based on the value of a tag that is named Business-Unit.Company leaders instruct developers to update all EC2 resources with the tag.The developers notify the leaders that they have completed this task.Later that week, a finance team member checks Cost Explorer.The finance team member sees EC2 costs in the different accounts but cannot find the Business-Unit tag to filter by or group by.

What is the MOST likely reason that the Business-Unit tag is absent?

The Business-Unit tag is not activated as a cost allocation tag in the AWS Billing and Cost Management console.

The Business-Unit tag is not valid because tag key names do not support dashes (-).

The instances have been rebooted, and the developers neglected to re-add the Business-Unit tag after the reboot.

The IAM user does not have permission to view the tags in Cost Explorer.

Explanations:

Cost allocation tags must be activated in the AWS Billing and Cost Management console for them to appear in Cost Explorer. Without activation, tags cannot be used to filter or group cost data.

Dashes (-) are valid characters in tag keys, so the format of the tag keyBusiness-Unitis not an issue.

Rebooting instances does not remove tags; tags persist across instance reboots.

Tag visibility in Cost Explorer does not depend on specific IAM permissions. If the tag is not activated as a cost allocation tag, it will not appear in Cost Explorer, regardless of permissions.

2025-10-07

1 Comment

  1. Luke
    Author

    From what I’ve heard, the answer is:
    The Business-Unit tag is not activated as a cost allocation tag in the AWS Billing and Cost Management console.

Leave a Reply

Your email address will not be published. Required fields are marked *

16 − 7 =