Course contentsShow
← Cloud and Infrastructure
Lesson 384 of 2,9897. Identity and Access ManagementFree lesson

AWS Organizations and SCPs

Service Control Policies to set permission guardrails across AWS Organizations accounts.

AWS Organizations and SCPs

You'll learn how to use Service Control Policies (SCPs) to set permission guardrails across all accounts in your AWS Organization.

What Are AWS Organizations?

AWS Organizations lets you centrally manage multiple AWS accounts as a single unit. Think of it like a corporate headquarters managing multiple branch offices—each branch (account) operates independently, but headquarters sets company-wide rules everyone must follow.

Service Control Policies: The Guardrails

Service Control Policies (SCPs) are the permission boundaries you attach to your AWS Organizations structure. While IAM policies grant permissions to individual users and roles, SCPs set maximum permissions across entire accounts or organizational units (OUs).

The key distinction: SCPs don't grant permissions—they limit what can be done, even if an IAM policy allows it. An SCP acts like a fence around your accounts, saying "nobody in this account can do X, regardless of their IAM permissions."

How SCPs Work

When a user makes an AWS API request, AWS checks:

  1. Does their IAM policy allow this action?
  2. Does the account's SCP allow this action?

Both must say "yes" for the action to succeed. This is policy evaluation logic applied at the organization level.

Common SCP Use Cases

  • Prevent deletion of CloudTrail logs across all accounts
  • Block specific AWS regions from being used
  • Enforce MFA requirements organization-wide
  • Restrict creation of expensive resource types

Key Takeaway: SCPs in AWS Organizations act as permission guardrails that limit what IAM policies can grant, ensuring compliance and security standards across all accounts in your organization—even administrators cannot bypass them.