AWS Organizations and Consolidated Billing

Why grouping accounts matters

Most organizations do not run everything in a single AWS account. They split workloads across many accounts: one for production, one for testing, separate accounts per team or per project. Separate accounts give you a clean security boundary and a clear cost boundary, but they create a new problem. Who pays all those bills, and how do you see the total in one place?

AWS Organizations answers that. It lets you group many AWS accounts under central management and bill them together. This lesson covers what an organization is made of and how consolidated billing turns many accounts into one bill, often at a lower total cost.

What AWS Organizations is

AWS Organizations is a free service for centrally managing multiple AWS accounts. You collect your accounts into an organization, arrange them in a tree, and manage billing and policies from the top.

An organization is built from a few parts:

• Management account: the account you use to create the organization. It owns the organization and acts as the payer account, responsible for paying all charges across every account. There is exactly one, and you cannot change which account it is.
• Member account: any other account that belongs to the organization. A member account can belong to only one organization at a time.
• Root: the top container in the hierarchy. AWS creates it automatically. Everything else sits under the root.
• Organizational unit (OU): a group of accounts under the root. OUs can be nested, so you can group accounts by department, environment, or workload and apply the same controls to all of them at once.

You add accounts in two ways: create brand-new member accounts from the management account, or invite existing standalone accounts to join. An invitation is a handshake the other account accepts.

The two feature sets

When you create an organization, you choose one of two feature sets. This choice decides how much the organization can do.

All features is the default and the recommended choice, because it adds governance tools like service control policies (SCPs), which set guardrails on what member accounts can do. If you start with consolidated billing only, you can upgrade to all features later, but every invited member account has to approve the change.

For the exam, remember the split: consolidated billing is billing only; all features adds the management and policy controls on top.

How consolidated billing works

Consolidated billing is the feature that combines the charges of every account in the organization into a single bill paid by the management account. AWS lists four benefits:

• One bill: you get a single bill that covers multiple accounts instead of one invoice per account.
• Easy tracking: you can track charges across all accounts and download the combined cost and usage data.
• Combined usage: usage is added together across accounts, which shares volume pricing discounts, Reserved Instance discounts, and Savings Plans across the whole organization.
• No extra fee: consolidated billing is offered at no additional cost.

The combined usage benefit is the one that saves real money. AWS prices many services in tiers where the unit cost drops as you use more. When usage from all accounts is added together, you reach those cheaper tiers faster than any single account would on its own. The same pooling applies to reservations: if one account buys a Reserved Instance or a Savings Plan and does not fully use it, the unused benefit can apply to matching usage in another account in the organization.

Member account bills still exist, but they are informational only. The management account is what actually pays, and it can see a combined view of all charges as well as a per-account cost report.

A note on account separation

Using multiple accounts is a best practice, not a workaround. Each account is a natural boundary for both cost and security. You can tell exactly what a team or project spends because its resources live in its own account, and a problem in one account is isolated from the others. Consolidated billing lets you keep that separation while still paying one bill and sharing discounts.

A common recommendation is to keep the management account clean. Run your actual workloads in member accounts and reserve the management account for organization-level tasks. This keeps its invoice simple and avoids mixing org administration with day-to-day resources.

Exam tips

• AWS Organizations lets you centrally manage many AWS accounts and is free to use.
• The management account is the payer account; it pays all charges for the organization. There is only one, and you cannot change which account it is.
• Member accounts belong to one organization at a time. Their individual bills are informational only.
• Organizational units (OUs) group accounts and can be nested; the root is the top of the tree.
• The four consolidated billing benefits: one bill, easy tracking, combined usage (shared volume, Reserved Instance, and Savings Plans discounts), and no extra fee.
• Two feature sets: consolidated billing (billing only) and all features (adds SCPs and service integrations). All features is the default and recommended.
• Combined usage across accounts can lower cost by reaching volume tiers sooner and sharing reservations.