Skip to content
Cloud Governance Tools

Service control policies (SCPs): what it can block and where it stops

Service control policies (SCPs) is a AWS mechanism. AWS documents SCPs as an AWS Organizations policy type that sets the maximum available permissions for IAM users and roles in member accounts. It applies to iAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.

All mechanisms ยท AWS guardrails

AWS documents SCPs as an AWS Organizations policy type that sets the maximum available permissions for IAM users and roles in member accounts. SCPs grant no permissions; they are evaluated together with identity-based and resource-based policies, and the effective permissions are the intersection.

AWS documents an SCP as an AWS Organizations policy type that sets the maximum available permissions for IAM users and roles in member accounts. SCPs grant no permissions; the effective permissions are the intersection of the SCP with identity-based and resource-based policies. They apply to users, roles and the root user in member accounts, and do not affect the management account or service-linked roles.

Limits: a maximum document size of 10,240 characters, and at most 10 SCPs attached directly to a root, OU or account, with at least one always attached. To test, the IAM policy simulator evaluates SCPs for identity-based policies but does not surface the matched statements, and AWS recommends trying an SCP on a small set of accounts in a separate OU. 27 library entries use SCPs.

Documented limits

  • SCPs do not affect users or roles in the management account. (source)
  • SCPs do not affect service-linked roles. (source)
  • Maximum SCP document size is 10,240 characters. (source)
  • Each root, OU or account can have at most 10 directly attached SCPs, and at least one SCP must always stay attached. (source)

Testing before enforcement

AWS documents that the IAM policy simulator evaluates SCPs (condition keys and resource scoping in deny statements) for identity-based policies, but it does not surface the matched SCP statements and it does not support RCPs. (source)

The 27 library entries written in it

Where Act is behind

Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

Sources

  1. Service control policies (SCPs), read 10 Nov 2026
  2. Limit, read 10 Nov 2026
  3. Testing, read 10 Nov 2026

Last reviewed 16 Nov 2026.