Skip to content
Cloud Governance Tools

AWS offers four preventive mechanisms, each evaluated at a different layer

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

The 40 entries

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.
GuardrailCloudMechanismRisk classTested first
Deny member accounts leaving the organizationAWSService control policies (SCPs)Organization integritydocumented
Prevent root credentials management in member accountsAWSService control policies (SCPs)Identity and privilegedocumented
Deny the root user except for S3 bucket policy changesAWSService control policies (SCPs)Identity and privilegedocumented
Deny critical IAM user actionsAWSService control policies (SCPs)Identity and privilegedocumented
Deny creating or changing IAM federation providersAWSService control policies (SCPs)Identity and privilegedocumented
Prevent creating or expanding public connectivity for VPCsAWSService control policies (SCPs)Network perimeterdocumented
Deny billing, tax and account contact changesAWSService control policies (SCPs)Organization integritydocumented
Deny enabling and disabling AWS ConfigAWSService control policies (SCPs)Logging and monitoringdocumented
Deny modifications to specific CloudTrail trailsAWSService control policies (SCPs)Logging and monitoringdocumented
Deny disabling or modifying Amazon GuardDutyAWSService control policies (SCPs)Logging and monitoringdocumented
Deny deleting VPC flow logsAWSService control policies (SCPs)Logging and monitoringdocumented
Deny KMS key deletionAWSService control policies (SCPs)Encryption and keysdocumented
Enforce a 30-day KMS key deletion windowAWSService control policies (SCPs)Encryption and keysdocumented
Deny disabling default EBS encryptionAWSService control policies (SCPs)Encryption and keysdocumented
Require server-side encryption on S3 uploadsAWSService control policies (SCPs)Encryption and keysdocumented
Deny access outside approved RegionsAWSService control policies (SCPs)Region and residencydocumented
Deny enabling or disabling opt-in RegionsAWSService control policies (SCPs)Region and residencydocumented
Region deny that allows Bedrock cross-Region inferenceAWSService control policies (SCPs)AI servicesdocumented
Allow only approved Amazon Bedrock modelsAWSService control policies (SCPs)AI servicesdocumented
Deny Amazon Bedrock API keysAWSService control policies (SCPs)AI servicesdocumented
Limit Amazon Bedrock long-term API keys to under 30 daysAWSService control policies (SCPs)AI servicesdocumented
Deny IAM and account actions invoked from chat applicationsAWSService control policies (SCPs)AI servicesdocumented
Restrict EC2 launches to approved instance typesAWSService control policies (SCPs)Resource and costdocumented
Restrict AWS Marketplace subscription changesAWSService control policies (SCPs)Resource and costdocumented
Deny disabling block public access for AMIsAWSService control policies (SCPs)Public exposuredocumented
Deny AWS RAM sharing with external accountsAWSService control policies (SCPs)Data exfiltrationdocumented
Require IAM authentication on Lambda function URLsAWSService control policies (SCPs)Public exposuredocumented
Require HTTPS for access to resourcesAWSResource control policies (RCPs)Encryption and keysdocumented
Require TLS 1.2 or later for S3AWSResource control policies (RCPs)Encryption and keysdocumented
Deny changes to S3 Block Public Access at bucket levelAWSResource control policies (RCPs)Public exposuredocumented
Deny unauthenticated access to Cognito identity poolsAWSResource control policies (RCPs)Public exposuredocumented
Deny S3 customer-provided encryption keys (SSE-C)AWSResource control policies (RCPs)Encryption and keysdocumented
Restrict access to resources in a suspended OUAWSResource control policies (RCPs)Organization integritydocumented
Block internet gateway ingress for VPCs (declarative policy)AWSDeclarative policiesNetwork perimeterdocumented
Block public sharing of EBS snapshots (declarative policy)AWSDeclarative policiesData exfiltrationdocumented
Require IMDSv2 for new EC2 instances (declarative policy)AWSDeclarative policiesIdentity and privilegedocumented
Enforce an Amazon Bedrock guardrail on model inference (declarative policy)AWSDeclarative policiesAI servicesnone found
Opt out of AI service content use organization-wide (declarative policy)AWSDeclarative policiesAI servicesdocumented
Permissions boundary limiting a user to S3, CloudWatch and EC2AWSIAM permissions boundariesIdentity and privilegedocumented
Permissions boundary for delegated IAM user creationAWSIAM permissions boundariesIdentity and privilegedocumented

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.

Sources

  1. Service control policies (SCPs), read 10 Nov 2026
  2. Resource control policies (RCPs), read 10 Nov 2026
  3. IAM permissions boundaries, read 10 Nov 2026
  4. Declarative policies, read 10 Nov 2026

Last reviewed 16 Nov 2026.