Declarative policies: what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Declarative policies is a AWS mechanism. AWS 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.
All mechanisms ยท AWS guardrails
AWS 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.
AWS documents declarative policies as an 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. They apply to a supported service attribute in the accounts, OUs or organization they are attached to, including actions by service-linked roles.
Limits: a maximum document size of 10,000 characters, and an EC2 declarative policy cannot be changed by account administrators, so any noncompliant action fails. AWS says detaching the policy rolls the attribute back to its previous state. The testing path is an account status report showing the current status of supported attributes. 5 library entries use declarative policies.
Documented limits
- Declarative policies are enforced in the service control plane, not as API authorization. (source)
- Maximum declarative policy document size is 10,000 characters. (source)
- Account administrators cannot change an attribute set by an EC2 declarative policy, and any noncompliant action fails. (source)
- AWS documents that detaching a declarative policy rolls the attribute back to its previous state. (source)
Testing before enforcement
AWS documents an account status report that shows the current status of the attributes supported by declarative policies for the accounts in scope. (source)
The 5 library entries written in it
- Block internet gateway ingress for VPCs (declarative policy)AWS, Declarative policies, network perimeter
- Block public sharing of EBS snapshots (declarative policy)AWS, Declarative policies, data exfiltration
- Require IMDSv2 for new EC2 instances (declarative policy)AWS, Declarative policies, identity and privilege
- Enforce an Amazon Bedrock guardrail on model inference (declarative policy)AWS, Declarative policies, ai services
- Opt out of AI service content use organization-wide (declarative policy)AWS, Declarative policies, ai services
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
- Declarative policies, read 10 Nov 2026
- Limit, read 10 Nov 2026
- Limit, read 10 Nov 2026
Last reviewed 16 Nov 2026.