Service control policy
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
An AWS Organizations policy that sets the maximum permissions for IAM users and roles in member accounts. It never grants access. It is attached to the root, an OU or an account, and the effective permissions are the intersection of the SCPs with the identity and resource policies.
An example, sourced
AWS documents that for a permission to be allowed in an account, an explicit Allow must exist at every level from the root through each OU to the account. When SCPs are enabled, AWS attaches a managed policy named FullAWSAccess to every root, OU and account. A Deny at any level on that path blocks the permission below it. A Deny-only SCP at the root, with no Allow, blocks every service.
Why it matters here
SCPs are the main preventive mechanism on AWS. Their evaluation rule explains most surprises, including the account where a new deny seems to do nothing because the principal sits in the management account. They also leave resources and outside principals alone, so decide early which risks need a resource control policy as well.
Related pages
Sources
- https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_evaluation.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.