INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: IAM: roles and permission limits

SCPs vs IAM policies: Organizations permission limits and scope

An SCP (Service Control Policy) controls the maximum available permissions for covered principals in AWS Organizations accounts. It does not replace IAM permission grants. Use a member account containing a report role to distinguish organization hierarchy, IAM grants and applicability.

What you will learn

Follow the root/OU/account path and explain its Allow/Deny rules, IAM grants and exceptions such as the management account.

Prerequisite

Know IAM grants and explicit/implicit denials. Organizations centrally manages AWS accounts; an OU (Organizational Unit) groups accounts or other OUs. SCPs require all features, rather than consolidated billing alone.

Distinguish the organization root, OU and account

Membership path to the report member account
Membership path to the report member account1: Organization root — Organization hierarchy; SCPs at this level are on the path. — Reports OU. 2: Reports OU — An account within this OU; not a credential or permission-transfer connection. — Member B12Organization rootReports OUMember BMembership path to the report member account1: Organization root — Organization hierarchy; SCPs at this level are on the path. — Reports OU. 2: Reports OU — An account within this OU; not a credential or permission-transfer connection. — Member B12OrganizationrootReports OUMember B
  1. Organization root → Reports OUOrganization hierarchy; SCPs at this level are on the path.
  2. Reports OU → Member BAn account within this OU; not a credential or permission-transfer connection.
Organization root
Top-level organization container; not an account’s root user.
Reports OU
An OU grouping report accounts.
Member B
The AWS account containing ReportReader.

The organization root, an AWS account and an account’s root user are different. The organization root and OUs are hierarchy containers; an account holds resources and IAM identities; its root user is a special principal. Management versus member account status also affects SCP applicability.

IAM grants and SCP limits have different jobs

Separate report-read permission into a grant and a guardrail
DimensionIAM permissions policies and grantsSCP
RoleGrant or deny access through identities or resourcesLimit available permissions of covered principals
AttachmentUsers/roles or supported resourcesOrganization root, OUs or accounts
Meaning of AllowCan provide a permission grantPlaces an action inside the SCP ceiling, not a grant
Reading a reportNeeds a suitable grant and other conditionsThe action must also be permitted along its applicable SCP path

Choose an option to see the result and explanation.

Every SCP level permits GetObject. Can the role read without a suitable grant?
Read the answer and reason

Answer: No: SCPs do not grant access · An SCP defines available scope. A suitable grant through role/resource permissions and other conditions still has to be established.

Read along the hierarchy and across policies at each level

Independent synthetic cases for the same ReportReader GetObject
CaseOrganization rootReports OUMember BSCP-side result
AAllowAllowAllowInside the ceiling; still not a grant
BAllowNo AllowAllowImplicitly denied at the OU level
CAllowAllow plus applicable DenyAllowExplicitly denied at the OU
DAllowNarrow Allow plus FullAWSAccessAllowThe broad same-level Allow also contributes

An Allow is needed at every level on the account’s path. Multiple SCPs at the same level contribute their Allows together. A narrow allowlist does not become the sole ceiling if FullAWSAccess remains at that level. An applicable explicit Deny anywhere on the path cannot be canceled by an Allow elsewhere.

Choose an option to see the result and explanation.

Root and account have Allow, but the intervening OU has none. What is the SCP-side result?
Read the answer and reason

Answer: Denied: the OU level on the path does not permit it · Permission must survive every applicable level. A lower-level Allow cannot override missing permission or an applicable Deny elsewhere on the path.

Do not treat management, outside and service principals alike

Identify the principal and the account it belongs to
Principal/configurationSCP applicabilityCaveat
IAM principal in a member accountCoveredIncludes delegated-administrator member accounts
Member-account root userCoveredNot a blanket bypass; specific documented task exceptions are separate
User/role in the management accountNot restricted by SCPsThis does not remove the need for other safeguards
Service-linked roleUnaffected by SCPsDo not generalize this exception to every service role
Outside principal directly accessing a resourceResource owner’s SCP does not directly restrict that outside principalCheck separate RCP/resource-policy and other controls

Direct access by an outside principal differs from assuming a role in member B and requesting as that session. The latter uses B’s role session, so check the SCPs applicable to that principal in B. Resource location alone does not identify the applicable SCPs.

Choose an option to see the result and explanation.

Are a management-account role and a member-account role equally restricted by SCPs?
Read the answer and reason

Answer: No: management-account users/roles are outside SCP restrictions · SCPs restrict covered member-account principals, not users/roles in the management account. A delegated-administrator member account is not the management account.

Review the request and hierarchy without changing organization settings

  1. Identify the caller’s account and management/member/outside status.
  2. Record the root, every OU and the target account on its path.
  3. Inspect relevant Allow and Deny across all SCPs at each level.
  4. Separately check IAM/resource grants and boundary/session/RCP controls.
  5. Report evidence and unknowns to the organization administrator; do not test by removing SCPs or changing FullAWSAccess attachments.

Check, then explain in your own words

  1. Explain why SCPs do not grant.
  2. Separate same-level Allows from restrictions along the hierarchy.
  3. Check principal ownership and management/service-linked exceptions.
Check your understanding: Does AdministratorAccess bypass a member account’s applicable SCP limits?

No. Broad IAM grants and applicable SCP ceilings are separate.

An IAM Allow does not cancel the applicable SCP path. Fix principal coverage and hierarchy, then separately check the required grants.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.