AWS offers four preventive mechanisms, each evaluated at a different layer
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
The library holds 40 AWS guardrails across 10 risk classes, written in Service control policies (SCPs), Resource control policies (RCPs), IAM permissions boundaries, Declarative policies. 39 of them have a documented way to test the effect before enforcing. Each entry copies the policy text from AWS documentation or a licensed open source set and says what it blocks and breaks.
All guardrails ยท AWS mechanisms
AWS documents SCPs and RCPs as AWS Organizations policy types that set the maximum available permissions, and both grant nothing. An SCP caps the IAM users, roles and root user in member accounts. An RCP caps the resources of supported services in member accounts, for any principal calling them, whether or not the caller belongs to the organization. Neither affects the management account or service-linked roles. Evaluation is by intersection: SCPs and RCPs are evaluated together with identity-based and resource-based policies, and the effective permissions are what all layers allow.
A permissions boundary works inside one account, on one IAM user or role, and caps what that entity's identity-based policies can grant. Declarative policies are different in kind: they enforce a baseline configuration in the service control plane, including for service-linked roles, so a noncompliant action fails, and detaching the policy rolls the attribute back. The library holds 40 AWS entries: 27 SCPs, 6 RCPs, 5 declarative policies and 2 permissions boundaries.
The mechanisms
- Service control policies (SCPs)AWS documents SCPs as an AWS Organizations policy type that sets the maximum available permissions for IAM users and roles in member accounts.
- Resource control policies (RCPs)AWS documents RCPs as an AWS Organizations policy type that sets the maximum available permissions for resources in member accounts.
- IAM permissions boundariesAWS documents a permissions boundary as a managed policy attached to an IAM user or role that sets the maximum permissions that an identity-based policy can grant to that entity.
- Declarative policiesAWS documents declarative policies as an AWS Organizations policy type that declares and enforces a baseline configuration for an AWS service in the service's control plane, rather than regulating API access the way SCPs and RCPs do.
The 40 entries
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- Service control policies (SCPs), read 10 Nov 2026
- Resource control policies (RCPs), read 10 Nov 2026
- IAM permissions boundaries, read 10 Nov 2026
- Declarative policies, read 10 Nov 2026
Last reviewed 16 Nov 2026.