Service control policies (SCPs): what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
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
- Deny member accounts leaving the organizationAWS, Service control policies (SCPs), organization integrity
- Prevent root credentials management in member accountsAWS, Service control policies (SCPs), identity and privilege
- Deny the root user except for S3 bucket policy changesAWS, Service control policies (SCPs), identity and privilege
- Deny critical IAM user actionsAWS, Service control policies (SCPs), identity and privilege
- Deny creating or changing IAM federation providersAWS, Service control policies (SCPs), identity and privilege
- Prevent creating or expanding public connectivity for VPCsAWS, Service control policies (SCPs), network perimeter
- Deny billing, tax and account contact changesAWS, Service control policies (SCPs), organization integrity
- Deny enabling and disabling AWS ConfigAWS, Service control policies (SCPs), logging and monitoring
- Deny modifications to specific CloudTrail trailsAWS, Service control policies (SCPs), logging and monitoring
- Deny disabling or modifying Amazon GuardDutyAWS, Service control policies (SCPs), logging and monitoring
- Deny deleting VPC flow logsAWS, Service control policies (SCPs), logging and monitoring
- Deny KMS key deletionAWS, Service control policies (SCPs), encryption and keys
- Enforce a 30-day KMS key deletion windowAWS, Service control policies (SCPs), encryption and keys
- Deny disabling default EBS encryptionAWS, Service control policies (SCPs), encryption and keys
- Require server-side encryption on S3 uploadsAWS, Service control policies (SCPs), encryption and keys
- Deny access outside approved RegionsAWS, Service control policies (SCPs), region and residency
- Deny enabling or disabling opt-in RegionsAWS, Service control policies (SCPs), region and residency
- Region deny that allows Bedrock cross-Region inferenceAWS, Service control policies (SCPs), ai services
- Allow only approved Amazon Bedrock modelsAWS, Service control policies (SCPs), ai services
- Deny Amazon Bedrock API keysAWS, Service control policies (SCPs), ai services
- Limit Amazon Bedrock long-term API keys to under 30 daysAWS, Service control policies (SCPs), ai services
- Deny IAM and account actions invoked from chat applicationsAWS, Service control policies (SCPs), ai services
- Restrict EC2 launches to approved instance typesAWS, Service control policies (SCPs), resource and cost
- Restrict AWS Marketplace subscription changesAWS, Service control policies (SCPs), resource and cost
- Deny disabling block public access for AMIsAWS, Service control policies (SCPs), public exposure
- Deny AWS RAM sharing with external accountsAWS, Service control policies (SCPs), data exfiltration
- Require IAM authentication on Lambda function URLsAWS, Service control policies (SCPs), public exposure
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.
Related pages
Sources
- Service control policies (SCPs), read 10 Nov 2026
- Limit, read 10 Nov 2026
- Testing, read 10 Nov 2026
Last reviewed 16 Nov 2026.