Tags not appearing in Cost Explorer

There are a few important points to consider regarding your S3 tagging and Cost Explorer issue:

First, for S3 specifically, cost allocation tags can only be applied to S3 buckets, not to individual objects within those buckets. While you can tag S3 objects for organizational purposes, these object-level tags won't appear in cost management tools like Tag Editor or Cost Explorer. Only bucket-level tags will be recognized for cost allocation.

For your bucket tags, even after activation in the Cost Allocation Tags section, there are several potential reasons why they might not be appearing in Cost Explorer:

1. Time delay: While you mentioned it's been more than a week, sometimes there can be processing delays beyond the typical 24-hour window.

2. Tag application: Double-check that the tags are correctly applied to the bucket resources themselves, not just activated in the Cost Allocation Tags section.

3. Resource charges: The tagged buckets must have actually incurred charges before Cost Explorer can show costs for the associated tags.

4. Account permissions: If you're using AWS Organizations, ensure you have the necessary permissions to access Cost Explorer with the activated tags.

If you're specifically trying to get cost breakdowns for each S3 bucket, you might want to:

• Verify the tags are applied at the bucket level (not just object level)
• Confirm the exact same tag keys are activated in Cost Allocation Tags
• Consider using AWS Cost and Usage Reports (CUR) for more detailed analysis if Cost Explorer continues to be problematic
  Sources
  S3 Tags Not Appearing in Tag Editor and Cost Explorer | AWS re:Post
  What are the reasons for Budget not working using cost filter with specific tags even after activating these tags in Cost Allocation Tags section ? | AWS re:Post
  Which AWS Services do not support cost allocation tagging | AWS re:Post

Hey,

Hope you're keeping well.

Cost Explorer only supports cost allocation tags at the resource level where AWS generates billing data. For S3, that means bucket-level tags are used, but object-level tags are not included in billing reports. Make sure the bucket tags are active under Billing > Cost Allocation Tags and are actually applied to the bucket in the S3 console. Also confirm that the tagged buckets have incurred charges in the period you’re viewing, as tags won’t appear if there’s no associated spend. If everything is set, new tag data generally appears within 24–48 hours in Cost Explorer, but for retroactive visibility you’ll need to check periods after activation.

Thanks and regards,
Taz