- Newest
- Most votes
- Most comments
I apologize, but there seems to be some confusion in your understanding of AWS Billing Conductor. Let me clarify based on the information available:
-
AWS Billing Conductor does not require a new linked AWS account. It is managed at the payer or management account level. There is no "Designated Billing Conductor Account" separate from the management account. All activities related to AWS Billing Conductor, such as creating billing groups, pricing plans, and viewing custom rates, are performed in the management (payer) account.
-
There is no separate account for AWS Billing Conductor. The service is accessed and managed through the payer or management account. The error message you're seeing suggests that you're trying to access the service from a linked account rather than the management account. AWS Billing Conductor is only accessible to users who have access to the payer or management account.
-
The AWS Cost and Usage Report (CUR) and AWS Cost Explorer in the management account will show both the actual AWS billing data and the pro forma costs created by AWS Billing Conductor. The pro forma costs represent the usage within Billing Conductor managed accounts at the pricing rates defined within the service. These pro forma costs do not change your actual AWS invoice but provide a customized view of costs based on your configured pricing plans and rules.
To use AWS Billing Conductor correctly:
- Log in to your management (payer) account
- Ensure you have the necessary IAM permissions to access and manage Billing Conductor
- Create billing groups to organize your accounts
- Set up pricing plans and rules as needed
- View the custom rates and pro forma costs in the Billing console or through generated Cost and Usage Reports for each billing group
Remember, AWS Billing Conductor is designed to create a second, customized version of your costs without affecting your actual AWS billing. It's primarily used for chargeback scenarios or to align costs with specific business requirements.
Sources
What is AWS Billing Conductor? - AWS Billing Conductor
AWS Billing Conductor – Amazon Web Services
Welcome - AWS Billing Conductor
Concepts and best practice for AWS Billing Conductor - AWS Billing Conductor
Item 2 does not seem to be correct.
During Set up of the "Billing Group" of "AWS Billing Conductor" service, I am required to choose a "Primary Account". The Management Account (Root) cannot be selected as a Primary Account for the Billing Group. Therefore I must select an account different from the Management Account (Root) -> new or existing linked account is required.
Therefore the question: What is the purpose of a separate account for "AWS Billing Conductor" especially when you say "everything" is managed in the Management Account.
Relevant content
- asked a year ago
- asked 4 months ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Kindly requesting support on below:
Item 2 from the "Bot Answer" seems incorrect.
During Set up of the "Billing Group" of "AWS Billing Conductor" service, I am required to choose a "Primary Account". The Management Account (Root) cannot be selected as a Primary Account for the Billing Group. Therefore I must select an account different from the Management Account (Root) -> new or existing linked account is required.
Therefore the question: What is the purpose of a separate account for "AWS Billing Conductor" especially when you say "everything" is managed in the Management Account.
Is there an overview of actions with Management account and "Primary Account for Billing Conductor"?