AWS Organizations
Cloud service · AWS · Updated

AWS Organizations

In short

AWS Organizations is a cloud service from Amazon Web Services that allows you to centrally manage and govern your environment as you scale your AWS resources across multiple accounts.

Cloud Services Hub →

Free AWS Organizations tools

5 key features of AWS Organizations

AWS Organizations provides centralized management, automated account creation, Service Control Policies for governance, consolidated billing for cost optimization, and customizable IAM roles and policies for enhanced security and compliance.

01
Centralized Management

AWS Organizations allows users to manage and govern their environment as they scale with AWS. By centrally managing policies across multiple AWS accounts, users can streamline operations and simplify compliance requirements.

02
Automated Account Creation

With AWS Organizations, users can automate the creation and management of new AWS accounts. This feature streamlines the process of expanding AWS resources and ensures new accounts adhere to company policies and security guidelines from the outset.

03
Service Control Policies

This feature enables users to apply policies that set maximum available permissions for IAM users and roles in member accounts, not the management account; SCPs do not grant permissions. Service Control Policies (SCPs) help ensure that accounts stay within the compliance and governance boundaries set by the organization.

04
Consolidated Billing

AWS Organizations offers consolidated billing for all accounts within the organization. This simplifies the billing process by aggregating usage across all accounts to a single payer account, potentially leading to lower overall costs.

05
Automatic Quota Increase Requests

Integration with Service Quotas lets you create a quota request template that automatically requests quota increases when accounts are created.

Where AWS Organizations is used

AWS Organizations enables centralized billing, automated account setup, enhanced security through policy enforcement, and efficient resource and access management across multiple AWS accounts.

  1. 01
    Centralized Billing Management

    AWS Organizations enables companies to consolidate billing across multiple AWS accounts, simplifying the process of tracking and managing cloud spending. Businesses can aggregate their AWS costs and access combined reports, allowing finance teams to easily monitor expenditures and budget more effectively.

  2. 02
    Automated Multi-account Setup

    Leveraging AWS Organizations allows for the automatic creation and management of AWS accounts according to the established policies and requirements of an enterprise. This streamlines the setup process for new projects or departments, ensuring consistency and compliance with company standards right from the start.

  3. 03
    Enhanced Security and Compliance

    With AWS Organizations, enterprises can apply service control policies (SCPs) across their AWS accounts to enforce compliance and security measures. This helps ensure that all accounts meet the company's security standards, significantly reducing the risk of violations and unauthorized access.

  4. 04
    Efficient Resource Management and Access Control

    AWS Organizations facilitates the grouping of AWS accounts into organizational units (OUs), enabling simplified management of resources, policies, and permissions. Administrators can apply policies at the OU level, streamline access control, and resource sharing across accounts, enhancing operational efficiency.

How AWS Organizations is priced

AWS Organizations offers a no-cost model for creating and managing an organization, including features like SCPs and consolidated billing, with costs only associated with the AWS resources used.

No Additional Charge

AWS Organizations is offered at no additional charge.

Service Control Policies (SCPs)

There is no additional charge for using SCPs within AWS Organizations to manage permissions. You pay for AWS resources used as defined by the service pricing.

Consolidated Billing

AWS Organizations offers consolidated billing for all the accounts in your organization at no extra charge. You benefit from volume pricing and can track charges and allocate costs across multiple accounts.

Services AWS Organizations works with

Amazon Bedrock

AWS Organizations can apply Amazon Bedrock policies that enforce designated guardrails across member accounts. This centralizes baseline safeguards for model inference without relying on each account to configure them independently.

Amazon CloudWatchAmazon CloudWatch

AWS Organizations enables organization-aware CloudWatch cross-account observability. A monitoring account can onboard source accounts by organization or organizational unit to view their metrics, logs, and traces centrally.

Amazon CodeGuruAmazon CodeGuru

AWS Organizations AI services opt-out policies can control whether Amazon CodeGuru Profiler uses collected content to improve its services. Policies inherited through organizational units provide consistent settings across member accounts.

Amazon ComprehendAmazon Comprehend

AWS Organizations AI services opt-out policies centrally control whether Amazon Comprehend may use customer content for service improvement. Administrators can apply the policy across the organization or selected organizational units.

Amazon ConnectAmazon Connect

AWS Organizations can apply AI services opt-out policies to supported Amazon Connect AI capabilities. This lets administrators centrally govern the use of customer content for service improvement across member accounts.

Amazon DetectiveAmazon Detective

AWS Organizations lets a delegated Amazon Detective administrator manage an organization behavior graph and enroll member accounts. Automatic enablement can add new organization accounts to the graph.

Amazon EC2Amazon EC2

AWS Organizations supports sharing EC2 AMIs with entire organizations or organizational units. Organizations declarative policies can also enforce supported EC2 account settings centrally, such as controls on public AMI access and allowed AMIs.

Amazon EventBridgeAmazon EventBridge

AWS Organizations membership can be used in EventBridge event-bus permissions to accept events from accounts throughout an organization. Organizations API activity delivered through CloudTrail can also trigger EventBridge rules, such as automation following account creation.

Amazon Fraud DetectorAmazon Fraud Detector

AWS Organizations AI services opt-out policies can centrally control whether Amazon Fraud Detector uses customer content for service improvement. The setting can be inherited by accounts within selected organizational units.

Amazon GuardDutyAmazon GuardDuty

AWS Organizations enables a delegated GuardDuty administrator to manage threat detection across member accounts. Organization configuration can automatically enable GuardDuty and supported protection plans for existing and newly added accounts.

What is AWS Organizations

3 min read

AWS Organizations is a robust service designed by Amazon Web Services (AWS) to help streamline the management and governance of multiple AWS accounts. With the adoption of cloud computing on a rise, organizations often find themselves handling an increasing number of AWS accounts. This surge can lead to complexity in billing, security, and compliance management. AWS Organizations addresses these challenges by offering a unified way to manage multiple accounts centrally. 

AWS Organizations is a global service; you do not need to select an AWS Region to operate it.

At the core of AWS Organizations is the concept of a management account and member accounts. The management account serves as the central control point, allowing administrators to create new accounts and invite existing accounts to join their organization. This hierarchical model enables the efficient distribution of shared resources, central policy management, and consolidated billing, thus simplifying the task of managing numerous accounts. 

One of the key features of AWS Organizations is Service Control Policies (SCPs). SCPs are akin to permissions that allow administrators to define and enforce policies across the entire organization or specific accounts within the organization. This level of control is instrumental in ensuring compliance with internal policies and external regulations. For instance, an SCP can restrict certain AWS services from being used, thus ensuring all members of the organization adhere to established IT governance standards. 

AWS Organizations supports two feature sets: consolidated billing only and all features. Policy-based governance, including SCPs, requires all features; consolidated billing only does not provide these governance controls.

Another significant benefit of AWS Organizations is the ability to streamline billing. By aggregating the billing of all member accounts, AWS Organizations enables the management account to benefit from consolidated billing. This not only reduces the administrative burden of managing multiple bills but also allows organizations to leverage volume discounts, as the combined usage across all accounts can qualify for tiered pricing discounts on many AWS services. 

AWS Organizations also supports automated account creation and management, which is a boon for large enterprises that need to provision and manage many AWS accounts efficiently. Through APIs, it integrates with other AWS services and third-party applications, allowing for the automation of account setup, resource deployment, and policy application. 

The default quota is 10 accounts per organization, and this quota is adjustable.

An account created in the organization must exist for at least four days before it can be removed from the organization.

The service enhances security and compliance by offering fine-grained control over AWS resources. The ability to apply policies at the organization, organizational unit (OU), or account level provides a flexible framework for enforcing security standards and compliance requirements. This is particularly valuable for organizations operating in regulated industries or those that need to adhere to strict internal security policies. 

In summary, AWS Organizations is an essential service for any organization looking to manage multiple AWS accounts efficiently. By facilitating centralized management, simplified billing, compliance enforcement, and enhanced security, AWS Organizations equips businesses with the tools they need to effectively govern their AWS environment, turning the complexity of cloud management into a streamlined and controlled process.

Concepts related to AWS Organizations

AWS Organizations exam questions

Real practice exam questions on AWS Organizations, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SOA-C03

A company uses AWS Organizations with all features enabled. A service-managed AWS CloudFormation StackSet deploys a monitoring baseline to member accounts in us-east-1. The company must extend the baseline to ap-east-1, an opt-in AWS Region, in the same accounts.

The management account has enabled ap-east-1, but the target member accounts show that Region as DISABLED. StackSet deployments to ap-east-1 fail. Trusted access is configured, the template supports ap-east-1, and no IAM policies or service control policies (SCPs) restrict the required operations.

Which solution will allow the engineer to deploy the baseline to ap-east-1 while retaining AWS-managed cross-account deployment permissions?

Show answerCORRECT ANSWER

Enable ap-east-1 in each target member account, wait until the Region status is ENABLED in those accounts, and then retry the StackSet deployments.

Opt-in Regions must be enabled separately for each target account. Enabling the Region only in the management account does not enable it in member accounts. After Region enablement completes, the existing service-managed StackSet can deploy there while retaining AWS-managed cross-account permissions.

SAP-C03

A company is preparing to divest a business unit that operates 24 AWS accounts. The accounts currently belong to the company's AWS Organizations organization. During the divestiture, the accounts will move to the buyer's organization in several waves. A transition agreement requires the company's tooling account to deploy and maintain a regional security baseline in all 24 accounts across three AWS Regions for 6 months, including after the accounts leave the company's organization.

The baseline has not yet been deployed. The company must manage it through one CloudFormation StackSet throughout the transition, without replacing the StackSet or transferring management of its stack instances. Account owners permit a one-time IAM bootstrap before the transition and will preserve explicitly configured deployment roles and cross-account trust relationships until the agreement ends. The tooling account cannot become a delegated administrator in the buyer's organization.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Create a self-managed StackSet. Bootstrap an administration role in the tooling account and an execution role in each target account, with the required cross-account trust and deployment permissions. Target the 24 account IDs and three Regions, and preserve those roles and trust relationships through the transition.

Self-managed StackSets can deploy to accounts regardless of organization membership when the necessary IAM roles and permissions exist. Creating the administration and execution roles establishes the required trust. Preserving those roles allows the same StackSet to continue managing its stack instances after accounts move to the buyer's organization.

CLF-C02

A company uses AWS Organizations consolidated billing. Its development, test, and production workloads run in separate member accounts. Each account contains resources for several products. Supported resources have a consistent Product tag, and the management account has already activated this tag for cost allocation. Finance needs an interactive report that combines each product's tagged resource costs across all three environments without changing the account structure. Which approach meets this requirement?

Show answerCORRECT ANSWER

Use AWS Cost Explorer in the management account, include all three member accounts, and group costs by the Product cost allocation tag.

An activated cost allocation tag provides a business-level reporting dimension. Grouping by Product across the included accounts combines each product's tagged resource costs even though its resources run in different environments.

Practice AWS Organizations in a full exam

Questions on AWS Organizations in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

Learn AWS Organizations in lessons

27 short lessons on AWS Organizations in 9 certification courses.

and 21 more lessons

Open the lessons

AWS architecture icons are the property of Amazon Web Services. BlowStack is not affiliated with or endorsed by AWS.