- Newest
- Most votes
- Most comments
Possible Causes:
Based on this behavior, the issue could be due to one of the following:
-
AWS Organizations Account Structure Issue • Linked2 (CCCCCCCCCC) may be incorrectly nested under Linked1 (BBBBBBBBBBB) instead of being directly linked to the management account.
-
Consolidated Billing Configuration • Linked2 may be mistakenly assigned to Linked1 for billing, instead of being billed directly by the management account.
-
AWS Cost Categories Misconfiguration • If Linked1 and Linked2 are part of the same Cost Category, AWS may be aggregating their charges under Linked1.
-
Cost Allocation Tags Grouping Costs Together • If Linked1 and Linked2 share the same Cost Allocation Tag, their charges may be combined under Linked1 in billing reports.
-
AWS Cost Explorer or Cost and Usage Report (CUR) Settings • The report settings might be grouping Linked2’s charges under Linked1.
Next Steps to Resolve the Issue:
Step 1: Verify AWS Organizations Account Hierarchy • Check if Linked2 is mistakenly nested under Linked1 instead of the management account. • Console Steps:
- Go to AWS Organizations Console.
- Navigate to Accounts and check the hierarchy. • CLI Command: aws organizations list-accounts
• Fix: If Linked2 is under Linked1, move it directly under the management account.
Step 2: Review AWS Consolidated Billing Settings • Ensure Linked2 is billed directly by the management account and not Linked1. • Console Steps:
- Go to AWS Billing Console.
- Click on Billing Preferences → Check the payer settings. • Fix: Update billing settings so that Linked2 is billed separately.
Step 3: Check AWS Cost Categories • Confirm whether Linked1 and Linked2 are grouped under the same cost category. • Console Steps:
- Go to AWS Billing Console → Cost Categories.
- Check if Linked1 and Linked2 are in the same category. • Fix: If they are grouped together, remove Linked2 from the shared cost category.
Step 4: Validate Cost Allocation Tags • Check if Linked1 and Linked2 share a tag that is aggregating their costs. • Console Steps:
- Go to AWS Billing Console → Cost Allocation Tags.
- Check the tags assigned to both accounts. • Fix: If they share a tag that combines costs, remove or modify the tag.
Step 5: Adjust AWS Cost Explorer Settings • Ensure costs are displayed per account without grouping. • Console Steps:
- Open AWS Cost Explorer.
- Select Group By: Account ID to see individual account costs. • Fix: Change the grouping settings to display accounts separately.
Next Steps for You:
Please review the steps above and let us know if you need further assistance. If the issue persists after these checks, we can escalate the case for deeper analysis.
[1] https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts.html [2] https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html [3] https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-cost-categories.html [4] https://repost.aws/knowledge-center/organizations-no-cost-allocation-tags [5] https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html
Please open billing conductor and review the profile groupings following:
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
