Service Control Policies (SCPs)
What you'll learn: How to enforce organization-wide permission limits across all AWS accounts from a single control point.
What Are SCPs?
Service Control Policies (SCPs) are top-level permission guardrails that apply across multiple AWS accounts within an AWS Organization. Think of them as a safety fence around your entire organization—no matter what individual IAM policies say, SCPs define the absolute outer boundary of what any identity can do.
An SCP doesn't grant permissions; it sets the maximum available permissions. Even if a user has full administrator access in their account, an SCP can block specific actions organization-wide.
The Guardrail Analogy
Imagine a school district (your AWS Organization) with multiple schools (accounts). Each school principal (account admin) can set rules for their building, but the district superintendent (SCP) can decree: "No one in any school may access the roof." Even if a principal gives a teacher roof access keys, the district policy overrides it.
How SCPs Work
SCPs attach to organizational units (OUs) or individual accounts. They use the same policy syntax you've learned—Effect, Action, Resource—but their impact cascades down the organization tree. If an SCP denies ec2:TerminateInstances, no one in affected accounts can delete EC2 instances, regardless of their IAM permissions.
SCPs are evaluated before identity-based and resource-based policies. The intersection of all policies determines final access.
Common Use Cases
- Prevent accounts from leaving specific regions
- Block deletion of critical resources
- Enforce MFA requirements organization-wide
- Disable specific AWS services across all accounts
Key Takeaway: SCPs are organization-level permission boundaries that enforce mandatory restrictions across all accounts, creating a safety net that no individual account policy can override.