Skip to content

AWS SCP – Service Control Policies

AWS Service Control Policies (SCPs) are a feature of the AWS Organizations service.

This feature is responsible for access control, restricting the actions that can be taken in an AWS account so that all IAM users and roles, including the root user, cannot perform them.

This allows you to centrally manage permissions across AWS accounts, enforcing security, compliance, and governance at an organizational level.

AWS SPC - Security Examples

Tips

  • Create multiple Organizational Units (OUs) instead of attaching all SCPs to the root of your organization. This approach allows for more granular restrictions and increases the number of SCPs you can attach, due to quota limits.
  • Each Organizational Unit (OU) can have up to 5 SCPs attached. To avoid hitting this limit, consider combining multiple policies into a single SCP where possible.
  • Refine your SCPs and restrict access to only the necessary AWS services using least privilege concept. Keep in mind that Root user accounts are affected by SCPs.
  • The default SCP is FullAWSAccess, which allows all actions. Use this as a base and then apply additional SCPs to restrict access as needed.
  • Unlike IAM policies, SCPs count whitespace towards the character limit. Be mindful of this when writing policies to ensure they stay within the size constraints.
  • Always test your SCPs in a non-production environment to understand their impact before applying them broadly.

Quotas

Value Quota
Maximum SCP attached to root 5
Maximum SCP attached per OU 5
Maximum SCP attached per account 5
Maximum size of a policy document 5120 characters