# AWS Organizations

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-organizations

> 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.

Practice exams covering AWS Organizations: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [AIB-C01 AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## Free AWS Organizations tools

- [AWS IAM Access Denied Decoder](https://blowstack.com/tools/aws-iam-access-denied-decoder): Tell whether a service or resource control policy denied a request, and find the policy.

## 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.

1. **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.
2. **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.
3. **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.
4. **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.
5. **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. **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. **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. **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. **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](https://blowstack.com/tools/cloud-services-hub/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 CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-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 CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-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 Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-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 Connect](https://blowstack.com/tools/cloud-services-hub/amazon-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 Detective](https://blowstack.com/tools/cloud-services-hub/amazon-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 EC2](https://blowstack.com/tools/cloud-services-hub/amazon-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 EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-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 Detector](https://blowstack.com/tools/cloud-services-hub/amazon-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 GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-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.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: AWS Organizations AI services opt-out policies can govern HealthLake's use of customer content for service improvement. Administrators can establish the setting centrally for member accounts.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: AWS Organizations enables a delegated Amazon Inspector administrator to manage vulnerability scanning across member accounts. The administrator can configure automatic activation for new accounts and review organization-wide findings and coverage.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: AWS Organizations AI services opt-out policies can control whether Amazon Lex uses customer content to improve its services. Applying the policy at the organization or organizational-unit level gives member accounts a consistent setting.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: AWS Organizations enables a delegated Macie administrator to manage member accounts and review their sensitive-data discovery findings. Automatic enablement can extend Macie coverage to newly added organization accounts.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: AWS Organizations supports Amazon Managed Grafana's service-managed access to data sources across member accounts. A workspace can target organizational units and use automatically provisioned roles to query supported AWS data sources in those accounts.
- **[Amazon Polly](https://blowstack.com/tools/cloud-services-hub/amazon-polly)**: AWS Organizations AI services opt-out policies can centrally control whether Amazon Polly uses customer content for service improvement. The policy can cover the entire organization or selected groups of accounts.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: AWS Organizations supports organization-wide administration of Amazon Q Developer profiles. A profile created for an organization can provide centrally managed Q Developer configuration to its member accounts.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: AWS Organizations supports sharing eligible Amazon Q Business subscriptions across accounts in the same organization. This allows supported applications to recognize an existing user subscription rather than requiring a separate subscription in each account.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: AWS Organizations AI services opt-out policies can centrally govern whether Amazon Rekognition uses customer content for service improvement. Policies can be inherited throughout the organization's account hierarchy.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: AWS Organizations integrates with S3 Storage Lens to provide storage-usage and activity visibility across member accounts. The management account or a delegated administrator can create organization-level dashboards instead of configuring separate reports in every account.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: AWS Organizations enables a delegated Security Lake administrator to configure security-data collection across member accounts. Organization settings can automatically onboard new accounts in selected Regions.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: AWS Organizations AI services opt-out policies can centrally control whether Amazon Textract uses customer content for service improvement. Administrators can enforce the setting across selected organizational units or the entire organization.
- **[Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe)**: AWS Organizations AI services opt-out policies can govern Amazon Transcribe's use of customer content for service improvement. This provides a centrally inherited setting for transcription workloads in member accounts.
- **[Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate)**: AWS Organizations AI services opt-out policies can centrally control whether Amazon Translate uses customer content for service improvement. A single organization policy can establish the setting across multiple accounts.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS Organizations enables VPC IP Address Manager to discover and manage IP address usage across member accounts through a delegated administrator. VPC Reachability Analyzer can also use Organizations integration to analyze network paths spanning accounts in the organization.
- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: AWS Organizations supports centralized administration of Application Migration Service across member accounts. A delegated administrator can manage organization-wide migrations without administering each account separately.
- **[AWS Artifact](https://blowstack.com/tools/cloud-services-hub/aws-artifact)**: AWS Organizations lets the management account accept eligible AWS Artifact agreements on behalf of the organization. Those organization agreements apply to member accounts, including accounts that subsequently join.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: AWS Organizations enables a delegated Audit Manager administrator to assess resources and collect audit evidence across member accounts. Assessments can include multiple organization accounts under centralized administration.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: AWS Organizations backup policies centrally define backup plans for member accounts and organizational units. AWS Backup also supports delegated administration and cross-account backup copies within an organization.
- **[AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management)**: AWS Organizations supplies the consolidated billing relationship used to combine member-account charges under the management account. Eligible volume discounts and reservation benefits can be shared across accounts according to billing preferences.
- **[AWS Billing Conductor](https://blowstack.com/tools/cloud-services-hub/aws-billing-conductor)**: AWS Organizations provides the member accounts that AWS Billing Conductor organizes into billing groups. Administrators can apply custom pricing rules to produce pro forma billing views for different groups of accounts.
- **[AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets)**: AWS Organizations consolidated billing lets the management account create budgets covering organization-wide spending or selected linked accounts. Budget filters can separate costs for individual member accounts while retaining centralized oversight.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: AWS Organizations chatbot policies centrally restrict supported chat applications and configuration options for AWS Chatbot in member accounts. These policies can establish organization-wide controls over where AWS chat integrations may be configured.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS Organizations integrates with CloudFormation StackSets to deploy stacks to accounts and organizational units using service-managed permissions, including automatic deployments when accounts join targeted units. CloudFormation also provides resource types for creating and managing Organizations resources such as accounts, organizational units, and policies.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS Organizations enables organization trails and organization event data stores that collect activity from member accounts. CloudTrail also records Organizations API calls, providing an audit history of account, policy, and organizational-unit changes.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: AWS Organizations lets Compute Optimizer analyze supported resources across member accounts. The management account can opt in the organization and delegate administration of organization-wide optimization recommendations.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Organizations enables organization-wide AWS Config rules, conformance packs, and configuration aggregators. A management or delegated administrator account can centrally deploy compliance checks and aggregate results from member accounts.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: AWS Organizations provides the accounts, organizational units, and policy hierarchy underlying a Control Tower landing zone. Control Tower uses that structure to enroll accounts, apply controls, and provision governed accounts through Account Factory.
- **[AWS Cost and Usage Report](https://blowstack.com/tools/cloud-services-hub/aws-cost-and-usage-report)**: AWS Organizations consolidated billing allows the management account's Cost and Usage Report to include usage and charges for member accounts. Account identifiers in the report support organization-wide cost allocation and analysis.
- **[AWS Cost Explorer](https://blowstack.com/tools/cloud-services-hub/aws-cost-explorer)**: AWS Organizations enables the management account to analyze consolidated cost and usage in Cost Explorer. Linked-account filters let administrators compare spending across member accounts and examine shared discount benefits.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: AWS Organizations works with AWS Data Exchange and AWS License Manager to distribute eligible data-product subscription entitlements to member accounts. This allows centrally purchased data subscriptions to be used by designated accounts in the organization.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: AWS Organizations lets AWS Directory Service share an AWS Managed Microsoft AD directory with accounts in the organization. Organization-based sharing avoids the invitation-and-acceptance workflow required for accounts outside the organization.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: AWS Organizations supplies the account and organizational-unit scope for Firewall Manager security policies. A Firewall Manager administrator can centrally apply supported firewall protections and automatically extend them to newly added accounts and resources.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: AWS Organizations enables AWS Health organizational view to aggregate health events affecting member accounts. The management account or a delegated administrator can monitor organization-wide service issues and scheduled changes.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: AWS Organizations enables an organization instance of IAM Identity Center to manage workforce access across member accounts. Administrators assign users and groups permission sets that provision corresponding IAM roles in the selected accounts.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: AWS Organizations service control policies set permission boundaries for IAM principals in member accounts, while resource control policies constrain supported resource access. IAM Access Analyzer also uses an organization as a zone of trust to identify resource access granted outside it.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Organizations can be used as the scope of a Lambda function's invocation permissions through the PrincipalOrgID setting. This grants invocation access to principals in the specified organization without listing each member account separately.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: AWS Organizations enables License Manager to discover and track license usage across member accounts through centralized administration. Organization integration also supports distributing granted licenses to eligible accounts.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: AWS Organizations underpins AMS multi-account landing zones, including account organization and centrally enforced policies. AMS uses this structure to provision and operate governed member accounts.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: AWS Organizations enables centralized administration of AWS Marketplace Private Marketplace, including delegated administration and procurement experiences scoped to organizational units. Eligible Marketplace licenses can also be distributed to member accounts through AWS License Manager.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: AWS Organizations enables RAM resource sharing with an entire organization or selected organizational units. Once organization sharing is enabled, member accounts can receive shared resources without accepting individual sharing invitations.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: AWS Organizations tag policies define tagging standards for member accounts. Resource Groups' tagging tools can evaluate resources against those policies and produce organization-wide tag-compliance reports.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: AWS Organizations enables delegated Security Hub administration and centralized security configuration across member accounts. Configuration policies can target organizational units to manage standards, controls, and service enablement consistently.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: AWS Organizations enables Service Catalog portfolio sharing with entire organizations or selected organizational units. Delegated administrators can manage these shares, and newly added accounts can inherit access to the portfolios shared with their organizational unit.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: AWS Organizations enables Systems Manager Quick Setup to deploy operational configurations across accounts and organizational units. Systems Manager Explorer and organization-wide node management can also use organization integration to centralize operational visibility.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: AWS Organizations enables Trusted Advisor organizational reporting to consolidate check results across member accounts. A management account or delegated administrator can identify recommendations affecting multiple accounts from a central view.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: AWS Organizations supports centralized administration of organization-wide AWS managed notifications through AWS User Notifications. A delegated administrator can manage notification delivery for events affecting member accounts.
- **[AWS Well-Architected Tool](https://blowstack.com/tools/cloud-services-hub/aws-well-architected-tool)**: AWS Organizations enables the Well-Architected Tool to share workloads and custom lenses with an organization or selected organizational units. This lets central architecture teams distribute review resources without inviting each account individually.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: AWS Organizations identifiers can be specified in EC2 Image Builder AMI distribution settings. Image Builder can grant launch permissions to an entire organization or selected organizational units as new AMIs are produced.

## What is AWS Organizations

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

- [Policy Inheritance](https://blowstack.com/tools/cloud-concepts-hub/policy-inheritance): Policy inheritance is the application of policies from a parent scope to its descendants according to defined evaluation and override rules.
- [Cost Allocation](https://blowstack.com/tools/cloud-concepts-hub/cost-allocation): Cost allocation is the process of assigning cloud expenses to the teams, applications, projects, or business units responsible for them.
- [Effective Permissions](https://blowstack.com/tools/cloud-concepts-hub/effective-permissions): Effective Permissions are the actions a principal is actually authorized to perform on a resource after all applicable policies, restrictions, and request conditions are evaluated.
- [Separation of Duties](https://blowstack.com/tools/cloud-concepts-hub/separation-of-duties): Separation of Duties divides sensitive responsibilities among independent people, roles, or teams so that no single actor controls an entire high-risk process.
- [Explicit Deny Precedence](https://blowstack.com/tools/cloud-concepts-hub/explicit-deny-precedence): Explicit Deny Precedence is the authorization rule that a matching explicit denial overrides otherwise applicable permissions.
- [Least privilege](https://blowstack.com/tools/cloud-concepts-hub/least-privilege): Least privilege means granting each identity or workload only the access required for its approved tasks, limited to the necessary resources, conditions, and duration.
- [Blast Radius](https://blowstack.com/tools/cloud-concepts-hub/blast-radius): Blast radius is the extent of resources, identities, data, and business functions that a failure, compromise, or erroneous change can affect.
- [Resource Tagging](https://blowstack.com/tools/cloud-concepts-hub/resource-tagging): Resource tagging is the practice of attaching key–value metadata to cloud resources so they can be organized, governed, automated, and associated with costs.
- [Data Sovereignty](https://blowstack.com/tools/cloud-concepts-hub/data-sovereignty): Data sovereignty is the principle that data is subject to the laws and governing authority of the jurisdictions that apply to it.
- [Data Residency](https://blowstack.com/tools/cloud-concepts-hub/data-residency): Data residency is the geographic location where data is stored and, when applicable requirements specify it, processed.
- [Management and governance](https://blowstack.com/tools/cloud-concepts-hub/management-and-governance): Management and governance is the combination of operating cloud resources and establishing the policies, responsibilities, and controls that keep their use aligned with business, security, and compliance requirements.
- [Volume Discounts](https://blowstack.com/tools/cloud-concepts-hub/volume-discounts): Volume discounts reduce the price per unit when eligible consumption or purchasing volume reaches defined thresholds.
- [Policy as Code](https://blowstack.com/tools/cloud-concepts-hub/policy-as-code): Policy as Code expresses governance and security requirements as version-controlled, machine-evaluable rules that automated workflows can test and enforce.
- [Allowlisting](https://blowstack.com/tools/cloud-concepts-hub/allowlisting): Allowlisting is a control approach that permits only explicitly approved entities, tools, or actions within a defined scope and denies everything else by default.
- [Break-Glass Access](https://blowstack.com/tools/cloud-concepts-hub/break-glass-access): Break-glass access is a preplanned, tightly controlled emergency access path used when normal administrative access is unavailable or insufficient to resolve a critical incident.
- [Multi-Factor Authentication](https://blowstack.com/tools/cloud-concepts-hub/multi-factor-authentication): Multi-factor authentication verifies an identity using two or more distinct categories of evidence before granting access.
- [Shadow AI](https://blowstack.com/tools/cloud-concepts-hub/shadow-ai): Shadow AI is the use of AI tools, models, or capabilities for organizational work without appropriate approval, visibility, or governance.
- [AWS Compliance](https://blowstack.com/tools/cloud-concepts-hub/aws-compliance): AWS Compliance is the practice of meeting and demonstrating applicable regulatory, industry, and contractual requirements for workloads running on AWS.
- [AWS Support plans](https://blowstack.com/tools/cloud-concepts-hub/aws-support-plans): AWS Support plans are support entitlements that determine the technical assistance, escalation options, and operational guidance available to an AWS customer.
- [Backup Isolation](https://blowstack.com/tools/cloud-concepts-hub/backup-isolation): Backup isolation separates recovery copies and their management controls from production systems so that a production compromise or failure does not also destroy the backups.
- [Consolidated billing](https://blowstack.com/tools/cloud-concepts-hub/consolidated-billing): Consolidated billing combines charges from multiple cloud accounts under a shared payment arrangement while retaining account-level usage and cost details.
- [Decision Rights](https://blowstack.com/tools/cloud-concepts-hub/decision-rights): Decision rights define who has authority to make, approve, challenge, and escalate specific decisions within an organization.
- [Discount sharing](https://blowstack.com/tools/cloud-concepts-hub/discount-sharing): Discount sharing allows eligible usage across accounts in a common billing group to benefit from pricing discounts available to that group.
- [Environment Isolation](https://blowstack.com/tools/cloud-concepts-hub/environment-isolation): Environment isolation separates development, testing, staging, and production resources so that activity in one environment does not unintentionally affect another.
- [Executive Sponsorship](https://blowstack.com/tools/cloud-concepts-hub/executive-sponsorship): Executive sponsorship is active, accountable support from a senior leader who authorizes resources, aligns stakeholders, and removes organizational barriers to a strategic initiative.
- [Hub-and-Spoke Model](https://blowstack.com/tools/cloud-concepts-hub/hub-and-spoke-model): The hub-and-spoke model combines a central team that provides shared expertise, standards, and capabilities with distributed teams that deliver solutions for their own business domains.
- [Privilege Escalation](https://blowstack.com/tools/cloud-concepts-hub/privilege-escalation): Privilege escalation is the acquisition of permissions beyond an identity’s intended authorization, often by exploiting excessive permissions, trust relationships, or control over privileged workloads.
- [Privileged Access Management](https://blowstack.com/tools/cloud-concepts-hub/privileged-access-management): Privileged Access Management is the practice of controlling, protecting, and auditing identities and sessions that can perform high-impact administrative actions.
- [Psychological Safety](https://blowstack.com/tools/cloud-concepts-hub/psychological-safety): Psychological safety is a shared belief that people can ask questions, raise concerns, admit mistakes, and challenge ideas without humiliation or unfair punishment.
- [Risk Appetite](https://blowstack.com/tools/cloud-concepts-hub/risk-appetite): Risk appetite is the amount and type of risk an organization is willing to accept while pursuing its objectives.
- [Role-Based Learning](https://blowstack.com/tools/cloud-concepts-hub/role-based-learning): Role-based learning is an approach to workforce development that tailors learning objectives, activities, and assessments to the responsibilities and decisions of each job role.
- [Tenant Isolation](https://blowstack.com/tools/cloud-concepts-hub/tenant-isolation): Tenant isolation is the enforcement of boundaries that prevent one tenant from accessing another tenant’s data or resources or exceeding its permitted use of shared capacity.
- [Trust Boundaries](https://blowstack.com/tools/cloud-concepts-hub/trust-boundaries): Trust boundaries are points where data, requests, or identities cross between environments with different security assumptions or levels of control.

## AWS Organizations exam questions

Real practice exam questions on AWS Organizations, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

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?

**Correct 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.

**Explanation:** 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.

### Question 2 (SAP-C03)

**Question:**

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?

**Correct 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.

**Explanation:** 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.

### Question 3 (CLF-C02)

**Question:**

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?

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

**Explanation:** 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.

### Question 4 (DEA-C01)

**Question:**

A company's management account in AWS Organizations has an account-level, multi-Region AWS CloudTrail Lake event data store that collects management events. Approved audit reports reference this event data store's ID and query its retained records. The organization has all features enabled, and trusted access for CloudTrail is enabled.

The company must expand collection to include future management events from all current and future member accounts. Existing records must remain queryable through the same event data store ID. Historical member-account events do not need to be collected.

Which solution meets these requirements with the least operational overhead?

**Correct answer:** From the management account, update the existing event data store to enable organization-wide collection. Keep multi-Region collection and management-event selection enabled.

**Explanation:** The management account can update an existing account-level event data store to become an organization event data store. This preserves the event data store ID and retained events while expanding future collection to organization accounts, including accounts that subsequently join. Multi-Region collection maintains coverage across Regions.

### Question 5 (AIP-C01)

**Question:**

A company runs foundation model applications in production member accounts managed through AWS Organizations. Application engineers propose changes to the business tools that each application can invoke. An independent AI risk team must approve every production tool-permission change before it takes effect.

An audit finds that engineers use different IAM roles to submit and approve changes, but can assume both roles. Engineers can also modify the deployment workflow and pass its execution role to other automation. Approval events are logged, but engineers administer the log destination.

The company needs an organization-wide control that prevents an engineer with compromised credentials from authorizing their own change, bypassing the approved deployment path, or removing the associated evidence. A separate central security team administers organizational controls and does not develop these applications.

Which design meets these requirements?

**Correct answer:** Use centrally controlled, non-overlapping engineer and risk-reviewer identities. Bind each approval to the exact proposed change and allow only a protected workflow execution role to apply it. Use SCPs and centrally administered IAM permissions and trust policies to block engineers from direct updates, assuming or passing privileged roles, and modifying the workflow or its controls. Store evidence under independent custody.

**Explanation:** This design separates proposing, approving, executing, and retaining evidence through effective access controls. Binding approval to the exact change prevents substitution after review. Protected workflow and role configuration prevent bypass, while independent log custody prevents engineers from removing evidence. SCPs establish permission boundaries; IAM policies and trust policies provide the necessary authorized access.

### Question 6 (SAA-C03)

**Question:**

A company uses AWS Organizations with consolidated billing for 25 member accounts. Each account belongs to a different application team. The central finance team needs to analyze organization-wide networking costs, while application engineers need to analyze NAT gateway and data transfer charges for only their own accounts. Engineers must not be able to view other teams' costs. The company wants to use native billing tools without exporting billing data or maintaining cross-account reporting roles. Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Enable linked-account access to AWS Cost Explorer in the management account. Grant engineers the required Cost Explorer read permissions in their own member accounts, and grant finance the required permissions in the management account.

**Explanation:** With linked-account access enabled, member accounts can use Cost Explorer to analyze their own costs without gaining visibility into other member accounts. Authorized users in the management account can analyze costs across the organization. This meets both visibility requirements without custom reporting or cross-account roles.

### Question 7 (SCS-C03)

**Question:**

A company uses AWS Organizations with all features enabled. A central S3 bucket is owned by a member account in the Security OU. Application roles in other member accounts read objects directly by using their existing role credentials. The bucket's only cross-account Allow statement permits s3:GetObject on the required objects and contains the following elements:

"Principal": "*",
"Condition": {
  "ForAnyValue:StringEquals": {
    "aws:PrincipalOrgPaths": "o-a1b2c3d4e5/r-ab12/ou-ab12-prod/"
  }
}

Reads from an application account succeed while the account is directly under the Production OU, ou-ab12-prod. After an administrator moves the account into a newly created child OU under Production, the same requests return AccessDenied. A simulation of only the application role's identity policies still returns allowed.

The role's identity policy allows the required reads. FullAWSAccess and RCPFullAWSAccess remain attached at every applicable organization level. No explicit denies, permissions boundaries, session policies, endpoint policies, or other restrictions affect the requests. The objects use SSE-S3 encryption and Bucket owner enforced Object Ownership.

The company must restore access and automatically support otherwise-authorized application roles in accounts directly under Production or anywhere below it. Accounts outside that subtree must not receive access through this bucket-policy statement. Which change meets these requirements?

**Correct answer:** Replace the condition with ForAnyValue:StringLike on aws:PrincipalOrgPaths, using the value o-a1b2c3d4e5/r-ab12/ou-ab12-prod/*.

**Explanation:** The account's organization path changes when it moves into the child OU. The existing exact match no longer supplies the required cross-account bucket-policy grant. ForAnyValue:StringLike supports the multivalued organization-path key and wildcard matching. The trailing wildcard matches both accounts directly under Production and accounts in descendant OUs, without matching accounts outside that subtree.

### Question 8 (DOP-C02)

**Question:**

A company uses AWS Organizations with all features enabled. A Workloads organizational unit (OU) is directly under the organization root and contains several child OUs. A separate SharedServices OU contains an account that owns an Amazon S3 bucket of approved account-bootstrap artifacts.

An onboarding workflow creates a BootstrapReader IAM role in each workload account. The role's identity policy allows s3:GetObject on the artifact bucket. The workflow then moves the account into Workloads or one of its descendants. No applicable SCP or other policy denies these reads.

The bucket must authorize cross-account reads by BootstrapReader roles only while their accounts belong to Workloads or its descendants. Accounts elsewhere in the organization and accounts that leave the organization must not receive this access. The solution must automatically accommodate new accounts, new child OUs, and account moves without updating account lists or the bucket policy. There are no other cross-account grants on the bucket.

Which solution meets these requirements?

**Correct answer:** Add a bucket-policy Allow for s3:GetObject on the artifact objects with Principal set to "*". Use ForAnyValue:StringLike on aws:PrincipalOrgPaths with the Workloads path o-<organization-id>/r-<root-id>/ou-<workloads-id>/*, and use ArnLike on aws:PrincipalArn to match arn:aws:iam::*:role/BootstrapReader.

**Explanation:** aws:PrincipalOrgPaths identifies the caller account's organization path. The wildcard after the Workloads OU matches both accounts directly in Workloads and accounts in descendant OUs. ForAnyValue:StringLike correctly evaluates this multivalued condition key. The ARN condition limits access to BootstrapReader roles. Membership changes are reflected in request context without maintaining account lists, and accounts outside the organization cannot satisfy the path condition.

### Question 9 (ANS-C01)

**Question:**

A financial services company routes internet-bound traffic from its workload accounts through a central inspection VPC. All workload accounts belong to a Workloads OU in AWS Organizations, which has all features enabled. New workload accounts are automatically placed in this OU. FullAWSAccess SCPs currently apply throughout the hierarchy.

Compliance requires that only the CentralNetworkProvisioner IAM role in each workload account can attach an internet gateway to a VPC. All other IAM principals, including member-account root users, must be prevented from performing this operation, even if they have AdministratorAccess. Permissions for unrelated API operations must remain unchanged. The company already centrally controls the provisioning, trust policies, and modification of the CentralNetworkProvisioner roles.

Which solution meets these requirements with the least ongoing administrative effort?

**Correct answer:** Attach an SCP to the Workloads OU that denies ec2:AttachInternetGateway on all resources when aws:PrincipalArn does not match arn:aws:iam::*:role/CentralNetworkProvisioner. Retain the existing FullAWSAccess SCPs and grant the role the required IAM permissions.

**Explanation:** The inherited explicit deny blocks internet gateway attachment by other principals in current and future OU member accounts, including member-account root users. The aws:PrincipalArn condition exempts sessions of the controlled role because requests made with role credentials use the IAM role ARN for this condition key. The exception does not grant permission, so the role still needs an IAM allow. Other API operations remain unaffected.

## Practice AWS Organizations in a full exam

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

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 69 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 49 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 40 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 25 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 23 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 23 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 12 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 9 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 3 questions
- [AIB-C01](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 1 question

## Learn AWS Organizations in lessons

27 short lessons on AWS Organizations in 9 certification courses.

- AIB-C01: AWS IAM and AWS Organizations: permissions versus guardrails (Premium), https://app.blowstack.com/lessons/aws-iam-and-aws-organizations-permissions-versus-guardrails-aib-c01
- SOA-C03: AWS Control Tower vs AWS Organizations: governance automation and organization management (Premium), https://app.blowstack.com/lessons/aws-control-tower-vs-aws-organizations-governance-automation-and-organization-management-soa-c03
- SAP-C03: AWS Control Tower vs AWS Organizations: governance responsibilities (Premium), https://app.blowstack.com/lessons/aws-control-tower-vs-aws-organizations-governance-responsibilities-sap-c03
- CLF-C02: AWS Control Tower vs AWS Organizations (Premium), https://app.blowstack.com/lessons/aws-control-tower-vs-aws-organizations-clf-c02
- DEA-C01: AWS Organizations vs AWS Identity and Access Management (IAM): Permission boundaries and grants (Premium), https://app.blowstack.com/lessons/aws-organizations-vs-aws-identity-and-access-management-iam-permission-boundaries-and-grants-dea-c01
- AIP-C01: AWS Organizations: SCP guardrails for foundation-model workloads (Premium), https://app.blowstack.com/lessons/aws-organizations-scp-guardrails-for-foundation-model-workloads-aip-c01
