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

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](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html))
- SCPs do not affect service-linked roles. ([source](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html))
- Maximum SCP document size is 10,240 characters. ([source](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html))
- Each root, OU or account can have at most 10 directly attached SCPs, and at least one SCP must always stay attached. ([source](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html))

## 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html))

## The 27 library entries written in it

- [Deny member accounts leaving the organization](/guardrails/aws-scp-deny-leave-org/): AWS, Service control policies (SCPs), organization integrity
- [Prevent root credentials management in member accounts](/guardrails/aws-scp-deny-member-root-credentials/): AWS, Service control policies (SCPs), identity and privilege
- [Deny the root user except for S3 bucket policy changes](/guardrails/aws-scp-deny-root-except-s3-bucket-policy/): AWS, Service control policies (SCPs), identity and privilege
- [Deny critical IAM user actions](/guardrails/aws-scp-deny-critical-iam-user-actions/): AWS, Service control policies (SCPs), identity and privilege
- [Deny creating or changing IAM federation providers](/guardrails/aws-scp-deny-iam-federation-changes/): AWS, Service control policies (SCPs), identity and privilege
- [Prevent creating or expanding public connectivity for VPCs](/guardrails/aws-scp-prevent-vpc-public-connectivity/): AWS, Service control policies (SCPs), network perimeter
- [Deny billing, tax and account contact changes](/guardrails/aws-scp-deny-billing-and-contact-changes/): AWS, Service control policies (SCPs), organization integrity
- [Deny enabling and disabling AWS Config](/guardrails/aws-scp-deny-config-changes/): AWS, Service control policies (SCPs), logging and monitoring
- [Deny modifications to specific CloudTrail trails](/guardrails/aws-scp-deny-cloudtrail-trail-changes/): AWS, Service control policies (SCPs), logging and monitoring
- [Deny disabling or modifying Amazon GuardDuty](/guardrails/aws-scp-deny-guardduty-changes/): AWS, Service control policies (SCPs), logging and monitoring
- [Deny deleting VPC flow logs](/guardrails/aws-scp-deny-vpc-flow-log-deletion/): AWS, Service control policies (SCPs), logging and monitoring
- [Deny KMS key deletion](/guardrails/aws-scp-deny-kms-key-deletion/): AWS, Service control policies (SCPs), encryption and keys
- [Enforce a 30-day KMS key deletion window](/guardrails/aws-scp-kms-30-day-deletion-window/): AWS, Service control policies (SCPs), encryption and keys
- [Deny disabling default EBS encryption](/guardrails/aws-scp-deny-disable-ebs-default-encryption/): AWS, Service control policies (SCPs), encryption and keys
- [Require server-side encryption on S3 uploads](/guardrails/aws-scp-require-s3-server-side-encryption/): AWS, Service control policies (SCPs), encryption and keys
- [Deny access outside approved Regions](/guardrails/aws-scp-deny-unapproved-regions/): AWS, Service control policies (SCPs), region and residency
- [Deny enabling or disabling opt-in Regions](/guardrails/aws-scp-deny-region-enable-disable/): AWS, Service control policies (SCPs), region and residency
- [Region deny that allows Bedrock cross-Region inference](/guardrails/aws-scp-region-deny-with-bedrock-cris/): AWS, Service control policies (SCPs), ai services
- [Allow only approved Amazon Bedrock models](/guardrails/aws-scp-bedrock-approved-models-only/): AWS, Service control policies (SCPs), ai services
- [Deny Amazon Bedrock API keys](/guardrails/aws-scp-deny-bedrock-api-keys/): AWS, Service control policies (SCPs), ai services
- [Limit Amazon Bedrock long-term API keys to under 30 days](/guardrails/aws-scp-bedrock-api-keys-max-30-days/): AWS, Service control policies (SCPs), ai services
- [Deny IAM and account actions invoked from chat applications](/guardrails/aws-scp-deny-chat-app-iam-actions/): AWS, Service control policies (SCPs), ai services
- [Restrict EC2 launches to approved instance types](/guardrails/aws-scp-restrict-ec2-instance-types/): AWS, Service control policies (SCPs), resource and cost
- [Restrict AWS Marketplace subscription changes](/guardrails/aws-scp-restrict-marketplace-subscriptions/): AWS, Service control policies (SCPs), resource and cost
- [Deny disabling block public access for AMIs](/guardrails/aws-scp-deny-disable-ami-block-public-access/): AWS, Service control policies (SCPs), public exposure
- [Deny AWS RAM sharing with external accounts](/guardrails/aws-scp-deny-ram-external-sharing/): AWS, Service control policies (SCPs), data exfiltration
- [Require IAM authentication on Lambda function URLs](/guardrails/aws-scp-require-lambda-url-iam-auth/): AWS, 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

- [Resource control policies (RCPs): how it works, its limits and how to test it](/mechanisms/rcp/)
- [IAM permissions boundaries: how it works, its limits and how to test it](/mechanisms/permissions-boundary/)
- [Declarative policies: how it works, its limits and how to test it](/mechanisms/declarative-policy/)

## Sources

- Service control policies (SCPs): https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html (read 10 Nov 2026)
- Limit: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html (read 10 Nov 2026)
- Testing: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/mechanisms/scp/
