Service Control Policies and Organizational Controls
What you'll learn: How Service Control Policies (SCPs) act as guardrails to restrict permissions across all accounts and organizational units in multi-account cloud environments.
The Central Governor Concept
Think of SCPs as the "master override switch" for your entire cloud organization. While IAM policies grant permissions to individual users and roles, SCPs set the maximum allowable permissions for entire accounts or groups of accounts. Even if a user has full administrator access via IAM policies, an SCP can block specific actions organization-wide.
How SCPs Work
SCPs apply at the organizational level, controlling what actions are possible within AWS accounts grouped in organizational units (OUs). They don't grant permissions—they define boundaries. A user needs both:
- An IAM policy that allows an action
- No SCP that denies that action
This creates a "double-lock" mechanism: both the SCP and IAM policy must permit an action.
Common Use Cases
Regulatory compliance: Prevent any account from launching resources in restricted regions, regardless of individual IAM policies.
Security baselines: Block all accounts from disabling CloudTrail logging or deleting security monitoring resources.
Cost control: Deny expensive instance types across development accounts while allowing them in production.
SCPs vs Permission Boundaries
While permission boundaries (from your previous lesson) limit individual IAM entities, SCPs control entire accounts. SCPs are the "organization's law," while permission boundaries are "departmental policies."
Key Takeaway: Service Control Policies provide centralized, enforceable guardrails across all accounts in an organization, creating a security boundary that no individual IAM policy can override—essential for maintaining consistent security posture in multi-account architectures.