- Newest
- Most votes
- Most comments
It is correct that you can only manage the user-defined cost allocation tags in the payer account. Some of the important points to remember when working with cost allocation tags is that you will have to:<br>
<ol> <li>Wait for 24 hours after you create the tag and assign to any resource to be visible in the payer account. </li> <li>Activate the cost allocation tag after its visible in payer accounts so it can appear in your Cost and Usage Reports, Cost Explorer. To see how to activate a user defined cost allocation tag, you will have to login to your management account (Payer account) and follow the steps shown in this documentation:<br> https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.htmlSecond item</li> <li>More importantly, you do not have to take any other action for the tag to be visible in the management account other than just waiting for 24 hours after creating and assigning it to a resource.</li> </ol> <br> You also might be interested to know that you can request backfill of your cost allocation tags for upto 12 months. <br> For example, the Project tag was activated in November 2023. On December 2023, you request to backfill the tag from January 2023. As a result, the Project tag is retroactively activated for the prior months from January to December 2023. The tag values corresponding to the Project tag will be available with the cost data after the backfill completes. This documentation link will guide you on the procedure for requesting a backfill for the cost allocation tag: <br> https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-allocation-backfill.html
Only the management account in an organization and single accounts that aren't members of an organization have access to the cost allocation tags manager in the Billing console.
if you try to configure it from the member account, you get the message as you have in you situation
so you need access to the Management account of your AWS organization, which is also a Payer account. You will see the configuration there:
Hi
https://repost.aws/knowledge-center/organizations-no-cost-allocation-tags
AWS cost allocation tags are managed at the payer account level. When an account moves to another organization, both user-defined and AWS-generated cost allocation tags previously activated for that account lose their "active" status and need to be activated again.
Relevant content
- asked 2 years ago
- Accepted Answerasked 9 months ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
okay I have created a resource group in prod account, after 24 hours it will be visible in payer account. One more question is: Is TAG Policy in AWS Organizations should be ENABLED ? because in my aws organization tag policy is disabled, should I also enable that too ? https://us-east-1.console.aws.amazon.com/organizations/v2/home/policies?region=us-east-1# Navigate to AWS Organizations > Policies There shows: "Tag policies Tag policies help you standardize tags on all tagged resources across your organization. You can use tag policies to define tag keys (including how they should be capitalized) and their allowed values." which is DISABLED
You do not have to enable the Tag policies for your cost allocation tags to work. Tag policies have different purpose in the sense that they help you standardize tags across resources in your organization's accounts. For example, a tag policy can specify that when the CostCenter tag is attached to a resource, it must use the case treatment and tag values that the tag policy defines. And this way you avoid people making mistakes in tagging the resources with different tags like Costcenter or costcenter, as these both will be treated as separate tags and if you do not activate them, they will not appear in cost allocation reports.
A tag policy can also specify that noncompliant tagging operations on specified resource types are enforced. In other words, noncompliant tagging requests on specified resource types are prevented from completing. Untagged resources or tags that aren't defined in the tag policy aren't evaluated for compliance with the tag policy. You can read more on tag policies here: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_tag-policies.html
Hello, Thanks for the guidance and help. Now the tag is showing in payer account and I activate that tag. Now should It take another 24 hours to show in cost explorer section ? Because its not showing in Cost Explorer section, when I try to select TAG, it shows nothing.