- Newest
- Most votes
- Most comments
Hello,
Here is an article from AWS explaining why you might not see cost allocation tags in the AWS Cost Explorer: https://repost.aws/knowledge-center/organizations-no-cost-allocation-tags.
I recommend using the AWS Tag Editor to ensure that all your AWS Config rules are appropriately tagged.
Additionally, with AWS Config, you are charged based on the number of configuration items recorded, the number of active AWS Config rule evaluations, and the number of conformance pack evaluations in your account. I doubt if we can filter the cost for the AWS Config service using user-defined tags, but any AWS experts can correct me if I'm wrong.
Hello,
After you have created and applied the user-defined tags, you have to activate by using the Billing and Cost Management console for cost allocation tracking and tags are not applied to resources that were created before the tags were created. [1]
Could you please confirm if you have activated user-defined tags in Billing and cost management console?
Hi Sivaraman, that's correct. The user-defined tags were enabled before implementing this solution.
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
Yes, all AWS Config rules were tagged using Tag Editor. Resources like aggregators and authorizations were tagged with the AWS CLI because Tag Editor does not support these resources.