Organizations manages account membership and policy inheritance. These sections separate billing, identity limits, resource limits, and service administration so each control has a clear purpose.
Organizations basics
AWS Organizations manages a group of AWS accounts as one organization, with shared billing and central policies.
How it works
- A management accountThe account that manages the organization and pays its member-account charges. creates the organization and creates or invites member accountsAn account belonging to an organization other than its management account..
- Accounts are grouped into organizational unitsA container grouping AWS accounts or other OUs for common management and policies..
- Policies apply to groups of accounts, and all usage lands on one consolidated bill.
Exam cues
- If the question says many accounts with one bill or central rules, think AWS Organizations.
Remember
- One consolidated bill for all accounts.
- Accounts stay separate, grouped in organizational units.
Trap: Organizations does not merge accounts. Each keeps its own resources and isolation; only billing and governance are central.
From the AWS docs (5)
- AWS Organizations centrally manages many AWS accounts: create accounts, group them, apply governance policies and pay with a single payment method.
- Organizations gives one consolidated bill for all member accounts, and usage across accounts can be viewed in Cost Explorer.
- The management account manages the organization and pays its member-account charges.
- An SCP limits the available permissions of principals in member accounts and never grants access.
- SCPs require the organization all-features mode and the SCP policy type enabled.
Accounts, OUs, and consolidated billing
AWS Organizations groups accounts for central management and billing. An organizational unitA container grouping AWS accounts or other OUs for common management and policies. (OU) is a folder for accounts or other OUs; policies inherited through that folder hierarchy apply to its accounts.
How it works
- Start with the organization rootThe top-level container for an organization account and OU hierarchy., the top folder, and a management accountThe account that manages the organization and pays its member-account charges., which manages the organization and pays member charges. Each account has one parent and belongs to one organization. The organization root is different from an account’s root userThe account-owner identity with access governed by AWS account and organization controls., its account-owner identityThe user, role, or service making an AWS request..
- Group accounts into OUs and attach applicable policies at the root, OU, or account level. Nested OUs inherit their parents’ policies.
- Create a new account or invite an existing one. Created accounts receive
OrganizationAccountAccessRoleby default; invited accounts do not. Cross-account access needs an access role and caller permission to assume it. - Choose the feature set. All features is the default and includes billing.
- Combine usage for eligible discounts. The management account controls Reserved InstanceAn AWS purchase whose eligible usage discount may be shared within an organization. and Savings Plans sharing; both the purchasing and receiving accounts must have sharing enabled. Consolidated billing has no added fee and produces one bill per Seller of RecordThe AWS entity responsible for issuing the applicable customer bill., the AWS entity issuing the bill.
When an account leaves, review roles that trust the former management account. They are not automatically deleted.
For activity alerts, configure a CloudTrail trailA CloudTrail configuration that records selected activity for an account or organization. and an EventBridge rule in us-east-1, with SNS as a notification target.
Exam cues
- If the question says an invited account lacks the administrative access role, think create the role explicitly, because invitation does not create it.
- If the question says discounts are not shared, think both accounts’ sharing settings, because one enabled side is insufficient.
Remember
- All features is the default.
- Billing combines charges and discounts, without granting resource access.
- Organization activity monitoring uses
us-east-1.
Trap: Moving an account does not automatically delete a role that trusts its former management account.
Root authorization policies apply down the organization hierarchy to member accounts.
The member account inherits applicable OU policies in addition to policies attached directly to it.
From the AWS docs (19)
- An organization groups AWS accounts under one root, with organizational units that can contain accounts and other OUs.
- An account belongs to only one organization and has one parent in that organization hierarchy.
- Accounts inherit applicable organization policies from their parent OUs and root.
- The management account manages the organization and pays its member-account charges.
- Consolidated billing combines payment but does not give the management account access to other accounts resources.
- Combined usage can qualify for volume pricing, Reserved Instance discounts, and Savings Plans discounts.
- Discount sharing requires both the purchasing account and the benefit-receiving account to have sharing enabled.
- The management account controls discount sharing preferences for organization accounts.
- Consolidated billing produces one bill per Seller of Record and has no additional fee.
- All features is the default feature set and includes consolidated billing and advanced organization management.
- Accounts created in Organizations receive OrganizationAccountAccessRole by default.
- Invited accounts do not automatically receive OrganizationAccountAccessRole; it can be created manually.
- Using OrganizationAccountAccessRole requires the management-account caller to have permission to assume it.
- Access roles trusting the old management account are not automatically removed when an account leaves.
- Account migration preparation includes checking organization-dependent policies and deregistering delegated administrator permissions.
- Organizations EventBridge monitoring is configured in US East (N. Virginia), us-east-1.
- A CloudTrail trail and EventBridge rule can monitor Organizations API actions and route notifications to SNS.
- The AWS account root user is the account identity created with access to all its services and resources, subject to applicable controls.
- AWS Organizations tag policies standardize the tags on resources across the organization's accounts, including the case of tag keys and values.
Service control policies
A service control policy (SCP) is an organization-wide permissions limit for member-account identities. A principalThe user, role, or service making an AWS request. is the identity making a request, such as a user or role. Passing SCP evaluation only leaves an action eligible; access still needs the appropriate IAM or resource policyA permissions policy attached to a resource that governs who may access it..
How it works
- Enable all features and the SCP policy type. Attach policies to the rootThe top-level container for an organization account and OU hierarchy., OUs, or accounts.
- Follow the account’s path from the root. An action needs an
Allowat every level, including the account. Any applicable explicitDenywins. - Choose a policy strategy. A deny listA policy strategy retaining broad eligibility while explicitly prohibiting selected actions. retains
FullAWSAccessor another suitable allow policy and adds restrictions. An allow listA policy strategy explicitly permitting selected actions while excluding unlisted actions. replaces broad allows with selected actions. A child cannot restore what an ancestor excludes. - Evaluate permissions inside that ceiling. Even
AdministratorAccesscannot override an SCP restriction. Member-account root usersThe account-owner identity with access governed by AWS account and organization controls. and delegated administratorsA member account registered to administer a specific integrated service for the organization. remain subject to SCPs, apart from documented exceptions. - Test restrictions on a limited set of accounts before widening their attachment.
For Config protection, denyA policy statement that blocks matching requests even when another applicable policy allows them. selected baseline changes: config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:PutConfigurationRecorder, config:PutDeliveryChannel, and config:StopConfigurationRecorder. A recorderThe Config component that captures resource configuration information. captures resource configurations; a delivery channelThe Config settings that direct recorded configuration data to its destinations. sends them to configured destinations. Conditions can preserve required administrative exceptions. Unrelated Config actions remain subject to their existing permissions.
Exam cues
- If the question says an IAM administrator is denied by an SCP, think the entire policy path, because IAM cannot override the ceiling.
- If the question says a deny-only SCP replaces
FullAWSAccess, think missing Allow, because a Deny statement does not supply the required Allow. - If the question says protect baseline Config without blocking all administration, think selected action denies, because SCPs can restrict specific operations.
Remember
- SCPs grant no permissions.
- The management accountThe account that manages the organization and pays its member-account charges. and service-linked roles are exempt.
- Member-account root users are restricted, with documented exceptions such as Enterprise Support enrollment and CloudFront trusted-signer functions.
- An SCP does not restrict external principals simply because they access a resource in your member accountAn account belonging to an organization other than its management account..
Trap: A delegated administrator is still a member account. Delegation does not exempt it from SCPs.
The root and every parent OU must allow the action. An applicable explicit Deny blocks it.
The account must also allow the action through its SCPs; IAM still needs to grant access.
From the AWS docs (17)
- An action needs an SCP Allow at every level from the root through each OU to the target account.
- An explicit SCP Deny at any point on the account path overrides allows at other levels.
- Organizations attaches FullAWSAccess to the root, OUs, and accounts by default to allow actions through SCP evaluation.
- Removing FullAWSAccess without another Allow at that level blocks actions for affected member principals.
- A deny-list SCP strategy retains FullAWSAccess or another Allow policy and adds Deny restrictions.
- An allow-list SCP strategy replaces broad allows with selected actions; lower levels cannot broaden an ancestor ceiling.
- AdministratorAccess cannot override a missing SCP Allow or an explicit SCP Deny.
- SCPs restrict member-account root users subject to the documented root-task exceptions.
- SCPs do not restrict the management account, but delegated administrator member accounts remain subject to them.
- SCPs do not restrict service-linked roles.
- SCP exceptions include root-user Enterprise Support enrollment and CloudFront trusted-signer functionality.
- SCPs on a resource-owning member account do not restrict principals in accounts outside that organization.
- An SCP can deny config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:PutConfigurationRecorder, config:PutDeliveryChannel, and config:StopConfigurationRecorder.
- SCP statements can deny selected actions with conditions, leaving other actions subject to their existing permissions.
- AWS recommends testing SCP impact on a limited set of accounts before broad attachment at the root.
- A principal is an identity that can make AWS requests, such as a user, role, or service.
- A Config recorder captures resource configurations, and its delivery channel selects destinations for recorded data.
Resource control policies
A resource control policy (RCP) limits access to supported resources in member accountsAn account belonging to an organization other than its management account., including requests from outside the organization. Think of it as a ceiling attached to the resource owner’s account hierarchy.
How it works
- Enable all features and RCPs. Confirm that the resource’s service supports RCPs; documented examples include S3, KMS, STS, SQS, and Secrets Manager.
RCPFullAWSAccesspermits requests through RCP evaluation but grants no resource access.- Attach RCPs where restrictions belong. A
Denyanywhere on the resource account’s path wins over a resource policyA permissions policy attached to a resource that governs who may access it. Allow. - Evaluate actual access with the relevant IAM and resource policies. A resource policy is a policy attached to a resource, such as an S3 bucket. It can grant access only within applicable organization limits.
- Test on a small scope before broader use. Management-account resources and calls made through service-linked roles are exempt; delegated administratorA member account registered to administer a specific integrated service for the organization. member-account resources remain covered.
| Control | What it limits | Grants access? |
|---|---|---|
| SCP | Member-account principalsThe user, role, or service making an AWS request. | No |
| RCP | Supported member-account resources, including outside access | No |
| Resource policy | Access to its attached resource | Can grant access within applicable limits |
Exam cues
- If the question says outside principals must be blocked from member-account S3 data, think RCP or bucket policy, because the bucket owner’s SCP does not constrain those outside identities.
- If the question says a bucket policy Allow conflicts with an RCP DenyA policy statement that blocks matching requests even when another applicable policy allows them., think denied, because the resource grant cannot override the ceiling.
Remember
RCPFullAWSAccessdoes not grant resource access.Principalsupports only*, andNotPrincipalis unsupported.- RCP coverage is service-specific; enabling RCPs does not restrict every AWS resource type.
Trap: An RCP passing a request does not grant it access. The required IAM or resource policy permissions must still exist.
The requester is outside the organization, but the resource is in a member account.
Access must pass the applicable RCP ceiling and the policies that grant access; an RCP Deny blocks it.
From the AWS docs (12)
- An RCP limits available permissions on supported resources in organization member accounts without granting access.
- An RCP on a member-account resource applies even when the requester belongs to an external account.
- SCPs constrain member-account principals, so a resource owner SCP does not restrict an external-account requester.
- RCPs require all-features mode and the RCP policy type enabled.
- RCP-supported services include S3, KMS, STS, SQS, and Secrets Manager; coverage is service-specific.
- RCPs can attach at the root, OU, or account and follow the resource-owning account hierarchy.
- Resources in the management account are exempt from RCPs; resources in delegated administrator member accounts are not.
- RCPs do not restrict calls made using service-linked roles.
- RCPFullAWSAccess permits requests through RCP evaluation without granting resource access.
- A Deny in any applicable RCP on the resource account path overrides a resource policy Allow.
- RCP Principal supports only the wildcard *; NotPrincipal is unsupported.
- AWS recommends testing RCP restrictions on individual accounts before applying them more broadly.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 22 cards as a list
A company with 30 AWS accounts wants one bill and central policies for all of them. Which service fits?
AWS Organizations, which gives consolidated billing and governance policies across accounts.
What billing feature does AWS Organizations provide?
Consolidated billing: one bill and one payment method for all member accounts.
Does AWS Organizations merge many accounts into one account?
No. Each account stays separate; Organizations groups and governs them and combines their bills.
A company wants to combine charges from multiple AWS accounts. How does AWS Organizations handle billing?
The management account pays member account charges through consolidated billing.
What does an AWS Organizations service control policy grant?
Nothing. An SCP sets the permission ceiling for member-account principals. IAM or resource policies must supply access within that ceiling, and SCPs require all-features mode.
Does AWS Organizations consolidated billing grant access to another member account resources?
No. It combines charges and eligible discounts. Cross-account administration still requires an access role and permission to assume it.
How does AWS Organizations organize accounts and apply inherited policies?
Accounts sit under the organization root or an OU. OUs can be nested, and applicable policies follow the parent path to each account.
A team invites an existing account to AWS Organizations but cannot find OrganizationAccountAccessRole. Why?
Organizations creates that role by default for newly created accounts, not invited accounts. Create it manually if needed, and authorize callers to assume it.
An account leaves AWS Organizations, but a role still trusts its old management account. Is that role removed automatically?
No. Remove or change the old access role deliberately; leaving the organization does not automatically delete it.
How can an AWS Organizations administrator receive an alert when an OU is created or an account attempts to leave?
Configure a CloudTrail trail and EventBridge rule in us-east-1, with SNS as a notification target.
Cost allocation reports break because teams tag resources as CostCenter, costcenter and cost-center. Which AWS Organizations feature enforces one standard?
Tag policies.
How are SCP permissions evaluated through nested AWS Organizations OUs?
The action needs an Allow at every level from root through the OUs to the account. An explicit Deny anywhere on that path wins.
An AWS Organizations administrator removes FullAWSAccess from the root and leaves only a deny-only SCP there. What happens?
Affected member principals lose the Allow at the root, blocking their actions. Keep FullAWSAccess for a deny-list strategy or replace it with suitable explicit allows.
A member-account administrator has AdministratorAccess but an operation is blocked by an AWS Organizations SCP. Can IAM override it?
No. The SCP ceiling still applies. Inspect every level on the account path for a missing Allow or explicit Deny.
Can an SCP restrict the root user, users, or roles in the AWS Organizations management account?
No. The management account is outside SCP restrictions. Delegated administrator member accounts remain restricted.
Which AWS Organizations principals and tasks are exempt from SCP restrictions?
The management account and service-linked roles are exempt. Some root-only tasks, including Enterprise Support enrollment and CloudFront trusted-signer functionality, are also exceptions. Member root users are otherwise restricted.
An AWS Organizations team must preserve baseline Config recording while leaving unrelated Config administration available. What SCP approach fits?
Deny the recorder/channel modification, deletion, and stop actions that must be protected, with any required administrative exceptions. Avoid denying all Config actions.
An AWS Organizations OU allow-list excludes an action, but the account-level SCP allows it. Is that sufficient?
No. A lower-level allow cannot broaden an ancestor ceiling. The action needs an Allow at every level and no applicable explicit Deny.
An S3 bucket in an AWS Organizations member account grants access to an external account. Does the bucket-owner SCP restrict that requester?
No. It limits member-account principals. Use an applicable RCP or a restrictive bucket policy to control external access to that bucket.
How do RCPs and SCPs differ in AWS Organizations?
RCPs limit supported member-account resources, including access by outside requesters. SCPs limit member-account principals. Neither grants access; management-account resources and service-linked-role calls are outside RCP restrictions.
An AWS Organizations team must centrally block outside principals from member-account resources. Can it rely on an SCP alone?
No. Use RCP restrictions for supported resources, alongside the policies that grant access. An SCP does not limit an external principal merely because the resource is in your organization.
An AWS Organizations RCP denies S3 reads, but the bucket policy grants them. Which policy wins?
The applicable RCP Deny wins. Resource-policy access must fit within the RCP ceiling.