AWS Consolidated Billing

• Consolidated billing enables consolidating payments from multiple AWS accounts (Linked or Member Accounts) within the organization to a single account by designating it to be the Management (formerly Payer) Account.
• Every organization in AWS Organizations has a management account that pays the charges of all the member accounts.
• Consolidated billing is automatically enabled when you create an AWS Organization and is offered at no additional cost.
• Consolidate billing
  • is strictly an accounting and billing feature.
  • allows receiving a combined view of charges incurred by all the associated accounts as well as each of the accounts.
  • is not a method for controlling accounts, or provisioning resources for accounts.
• Management account is billed for all charges of the member accounts.
• Each linked account is still an independent account in every other way.
• AWS Organization Consolidated Billing feature does not allow the Management account to access data belonging to the linked account owners. All Features mode needs to be enabled for organizational policies.
• However, access to the Management account users can be granted through Cross-Account Access roles.
• AWS limits work on the account level only and AWS support is per account only.
• All workload resources should reside only within member accounts and no resource should be created in the management account (AWS Well-Architected best practice).

Consolidated Billing Process

• AWS Organizations provides consolidated billing so that the combined costs of all the member accounts in your organization can be tracked.
• Create an Organization.
• Create member accounts or invite existing accounts to join the organization.
• Each month AWS charges your management account for all the member accounts in a consolidated bill.
• The consolidated bill is available within minutes and includes detailed breakdowns by account, service, and region.

Consolidated Billing Scenarios

• Have multiple accounts and want to get a single bill and track each account’s charges for e.g. multiple projects, each with its own AWS account or separate environments (Dev, Prod) within the same project.
• Have multiple cost centers to track.
• Have acquired a project or company with its own existing AWS account and you want a consolidated bill with your other AWS accounts.
• Have multiple organizations and want centralized billing management across them (using AWS Billing Transfer).

Consolidated Billing Benefits

• One Bill
  • A single bill with a combined view of AWS costs incurred by all accounts is generated.
• Easy Tracking
  • Detailed cost reports & charges for each of the individual AWS accounts associated with the management account can be easily tracked.
  • Use Cost Allocation Tags to categorize and track costs; tags are included in the detailed billing report.
• Combined Usage & Volume Discounts
  • Charges might actually decrease because AWS combines usage from all the accounts to qualify you for volume pricing discounts.
• Free Tier
  • Customers that use Consolidated Billing to consolidate payment across multiple accounts will only have access to one free usage tier and it is not combined across accounts.
• No Extra Cost
  • Consolidated billing is offered at no additional cost.

Volume Pricing Discounts

• For billing purposes, AWS treats all the accounts in the organization on the consolidated bill as if they were one account.
• AWS combines the usage from all accounts to determine which volume pricing tiers to apply, giving you a lower overall price whenever possible.
• This applies to services with tiered pricing such as S3 storage, data transfer, and DynamoDB.

Volume Discounts Example

• Example AWS Pricing – AWS charges $0.17/GB for the first 10 TB of data transfer out used, and $0.13/GB for the next 40 TB used that translates into $174.08 per TB for the first 10 TB, and $133.12 per TB for the next 40 TB.
• Usage – Bob uses 8 TB of data transfer out during the month, and Susan uses 4 TB (for a total of 12 TB used).
• Actual Individual Bill – AWS would have charged Bob and Susan each $174.08 per TB for their usage, for a total of $2088.96.
• Volume Discount Bill – Combined 12 TB total that Bob and Susan used, would cost the management account ($174.08 * 10 TB) + ($133.12 * 2 TB) = $1740.80 + $266.24 = $2007.04.

Reserved Instances and Savings Plans Sharing

• All member accounts in an Organization on a consolidated bill can receive the hourly cost-benefit of Reserved Instances (RIs) and Savings Plans that are purchased by any other account.
• The management account of an organization can turn off Reserved Instance and Savings Plans discount sharing for any accounts in that organization, including the management account.
• RIs and Savings Plans discounts aren’t shared between any accounts that have sharing turned off. To share an RI or Savings Plans discount with an account, both accounts must have sharing turned on.
• For e.g., Bob and Susan each have an account on Bob’s consolidated bill. Susan has 5 Reserved Instances of the same type, and Bob has none. During one particular hour, Susan uses 3 instances and Bob uses 6, for a total of 9 instances used on Bob’s consolidated bill. AWS will bill 5 as Reserved Instances, and the remaining 4 as normal instances.

RI and Savings Plans Group Sharing (Nov 2025)

• RISP Group Sharing provides granular control over how AWS commitments (RIs and Savings Plans) are shared across accounts within an organization.
• Allows defining groups of accounts (using AWS Cost Categories) based on business units, projects, regions, or funding sources.
• Two sharing options:
  • Prioritized Group Sharing – Applies commitments to defined groups first, then shares unused capacity organization-wide.
  • Restricted Group Sharing – Keeps commitments exclusively within defined groups for complete isolation when strict boundaries are required.
• Addresses the challenge of ensuring Reserved Instances and Savings Plans benefit the teams that actually purchased them.
• When using Billing Transfer, Reserved Instances and Savings Plans apply only to the AWS Organization where they were purchased and cannot be shared across multiple Organizations.

AWS Billing Transfer (Nov 2025)

• AWS Billing Transfer allows centralized billing management and payment across multiple AWS Organizations.
• Customers operating in multi-organization environments can designate a single management account to centrally manage and pay bills for multiple organizations.
• Capabilities include:
  • Centralized invoice collection across organizations.
  • Single payment processing for multiple organizations.
  • Detailed cost analysis spanning multiple organizations.
• Individual management accounts maintain complete security autonomy over their organizations.
• Integrated with AWS Billing Conductor to control how cost data is viewed by organizations and implement advanced cost allocation strategies.
• Pricing:
  • AWS managed pricing plan – No additional cost.
  • Customer managed pricing plan – $50/month per AWS Organization.
  • Free trial available through May 31, 2026.
• Available in all public AWS Regions (excluding GovCloud (US), China Beijing, and China Ningxia).

AWS Billing View & Custom Billing Views (2024-2025)

• AWS Billing View enables scoping and securely sharing exact cost and usage data access levels with stakeholders.
• Custom Billing Views represent a filtered view of cost management data that can be:
  • Shared with member accounts within an organization, giving business unit owners access to their cost data without management account access.
  • Shared with accounts outside the organization (multi-source views).
  • Combined from multiple organizations into consolidated multi-source views.
• Accessible through AWS Cost Explorer and AWS Budgets.
• Enables cross-account cost visibility in AWS Budgets without requiring management account access.

AWS Cost and Usage Report (CUR 2.0) & Data Exports

• AWS Data Exports enables creating recurring exports of billing and cost management data to S3.
• CUR 2.0 is gradually replacing the Legacy Cost and Usage Report with improvements:
  • Static schema for easier data ingestion.
  • Additional columns (usage account name, billing account name).
  • Collapsed columns to reduce data sparsity.
  • Supports FOCUS 1.2 specification for open-source cost data formatting.
• In AWS Organizations, both management accounts and member accounts can create Cost and Usage Reports.
• Split Cost Allocation Data enables cost visibility for containerized workloads (ECS tasks, EKS pods, AWS Batch jobs) across the entire consolidated billing family, including CPU, memory, and GPU/accelerator resource allocation.

Consolidated Billing Best Practices

• Paying account should be used solely for accounting and billing purposes
• Consolidated billing works best with Resource tagging, as tags are included in the detailed billing report, which enables cost to be analyzed and decomposed across multiple dimensions and aggregation levels.
• Paying account owners should secure their accounts by using MFA (multi-factor authentication) and a strong password

Consolidated Billing Best Practices (Current)

• Management account should be used solely for billing, governance, and organizational management—no workload resources should be created in it.
• Use Cost Allocation Tags to categorize and track costs; tags are included in the detailed billing report for analysis across multiple dimensions.
• Secure the management account with MFA, a strong password, and minimal IAM users.
• Use AWS Budgets to set cost thresholds and receive alerts.
• Use Billing View to delegate cost visibility to business unit owners without sharing management account access.
• Leverage RISP Group Sharing to align commitment discounts with the business units that purchased them.
• Use Service Control Policies (SCPs) with All Features mode for governance and access control.

AWS Certification Exam Practice Questions

• Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
• AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
• AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
• Open to further feedback, discussion and correction.

1. An organization is planning to create 5 different AWS accounts considering various security requirements. The organization wants to use a single payee account by using the consolidated billing option. Which of the below mentioned statements is true with respect to the above information?
   • Master (Payee) account will get only the total bill and cannot see the cost incurred by each account
   • Master (Payee) account can view only the AWS billing details of the linked accounts
   • It is not recommended to use consolidated billing since the payee account will have access to the linked accounts
   • Each AWS account needs to create an AWS billing policy to provide permission to the payee account
2. An organization has setup consolidated billing with 3 different AWS accounts. Which of the below mentioned advantages will organization receive in terms of the AWS pricing?
   • The consolidated billing does not bring any cost advantage for the organization
   • All AWS accounts will be charged for S3 storage by combining the total storage of each account
   • EC2 instances of each account will receive a total of 750*3 micro instance hours free
   • The free usage tier for all the 3 accounts will be 3 years and not a single year
3. An organization has added 3 of his AWS accounts to consolidated billing. One of the AWS accounts has purchased a Reserved Instance (RI) of a small instance size in the us-east-1a zone. All other AWS accounts are running instances of a small size in the same zone. What will happen in this case for the RI pricing?
   • Only the account that has purchased the RI will get the advantage of RI pricing
   • One instance of a small size and running in the us-east-1a zone of each AWS account will get the benefit of RI pricing
   • Any single instance from all the three accounts can get the benefit of AWS RI pricing if they are running in the same zone and are of the same size
   • If there are more than one instances of a small size running across multiple accounts in the same zone no one will get the benefit of RI
4. An organization is planning to use AWS for 5 different departments. The finance department is responsible to pay for all the accounts. However, they want the cost separation for each account to map with the right cost centre. How can the finance department achieve this?
   • Create 5 separate accounts and make them a part of one consolidated billing
   • Create 5 separate accounts and use the IAM cross account access with the roles for better management
   • Create 5 separate IAM users and set a different policy for their access
   • Create 5 separate IAM groups and add users as per the department’s employees
5. An AWS account wants to be part of the consolidated billing of his organization’s payee account. How can the owner of that account achieve this?
   • The payee account has to request AWS support to link the other accounts with his account
   • The owner of the linked account should add the payee account to his master account list from the billing console
   • The payee account will send a request to the linked account to be a part of consolidated billing (Check Process)
   • The owner of the linked account requests the payee account to add his account to consolidated billing
6. You are looking to migrate your Development (Dev) and Test environments to AWS. You have decided to use separate AWS accounts to host each environment. You plan to link each accounts bill to a Master AWS account using Consolidated Billing. To make sure you keep within budget you would like to implement a way for administrators in the Master account to have access to stop, delete and/or terminate resources in both the Dev and Test accounts. Identify which option will allow you to achieve this goal.
   • Create IAM users in the Master account with full Admin permissions. Create cross-account roles in the Dev and Test accounts that grant the Master account access to the resources in the account by inheriting permissions from the Master account.
   • Create IAM users and a cross-account role in the Master account that grants full Admin permissions to the Dev and Test accounts.
   • Create IAM users in the Master account. Create cross-account roles in the Dev and Test accounts that have full Admin permissions and grant the Master account access.
   • Link the accounts using Consolidated Billing. This will give IAM users in the Master account access to resources in the Dev and Test accounts
7. When using consolidated billing there are two account types. What are they?
   • Paying account and Linked account
   • Parent account and Child account
   • Main account and Sub account.
   • Main account and Secondary account.
8. A customer needs corporate IT governance and cost oversight of all AWS resources consumed by its divisions. The divisions want to maintain administrative control of the discrete AWS resources they consume and keep those resources separate from the resources of other divisions. Which of the following options, when used together will support the autonomy/control of divisions while enabling corporate IT to maintain governance and cost oversight? Choose 2 answers
   • Use AWS Consolidated Billing and disable AWS root account access for the child accounts. (Need to link accounts and disabling root access is just a best practice)
   • Enable IAM cross-account access for all corporate IT administrators in each child account. (Provides IT governance)
   • Create separate VPCs for each division within the corporate IT AWS account.
   • Use AWS Consolidated Billing to link the divisions’ accounts to a parent corporate account (Will provide cost oversight)
   • Write all child AWS CloudTrail and Amazon CloudWatch logs to each child account’s Amazon S3 ‘Log’ bucket (Preferred approach would be to store logs from multiple accounts to a single S3 bucket with CloudTrail for IT Governance and CloudWatch alerts for Cost Oversight)
9. An organization has 10 departments. The organization wants to track the AWS usage of each department. Which of the below mentioned options meets the requirement?
   1. Setup IAM groups for each department and track their usage
   2. Create separate accounts for each department, but use consolidated billing for payment and tracking
   3. Create separate accounts for each department and track them separately
   4. Setup IAM users for each department and track their usage
10. A large enterprise operates multiple AWS Organizations for different business units. They want to centralize invoice collection and payment processing while allowing each organization to maintain security autonomy. Which AWS feature should they use?
    • Create a single AWS Organization and move all accounts into it
    • Use IAM cross-account roles to access billing in each organization
    • Use AWS Billing Transfer to designate a single management account to centrally manage billing across multiple organizations
    • Enable consolidated billing in each organization and manually combine invoices
11. An organization has purchased Reserved Instances in Account A for the engineering team. They want to ensure the RI discounts benefit only the engineering team’s accounts (A, B, and C) and are NOT shared with other accounts in the organization. Which approach provides the most granular control?
    • Turn off RI sharing in the management account for all non-engineering accounts
    • Purchase Reserved Instances in a separate organization with only engineering accounts
    • Use Reserved Instances and Savings Plans Group Sharing with Restricted Group Sharing to limit discount sharing to the engineering group only
    • Create a Service Control Policy to prevent other accounts from using Reserved Instances
12. A company wants to give department managers visibility into their team’s AWS costs without providing access to the management account. Which AWS feature enables this?
    • Share IAM credentials for the management account billing console
    • Create Custom Billing Views and share them with department manager accounts
    • Enable all member accounts to create their own Cost and Usage Reports
    • Use AWS Billing Conductor to create separate pro forma bills

References

• AWS Consolidated Billing
• Reserved Instances and Savings Plans Discount Sharing
• AWS Billing Transfer
• AWS Billing View
• Cost and Usage Reports for Organizations
• RISP Group Sharing Announcement