Skip to content
Cloud Governance Tools

Region guardrails keep resources where the law says, and break global services that are not exempted

5 guardrails in the library address region and residency: 2 AWS, 2 Azure, 1 Google Cloud. The first in the list, "Deny access outside approved Regions", denies every action requested in a Region outside the approved list (eu-central-1 and eu-west-1 in the example), with a NotAction list that exempts global services, unless the caller is the privileged role.

All risk classes ยท Download the library

Guardrails in this class limit where resources can be created or used. The library holds 5. In AWS, denying access outside approved Regions breaks any global service missing from the exemption list, and the README warns the example may not include all the latest global services or operations. Azure's allowed locations definition returns 403 for deployments to other locations, and excludes resource groups and a few resource types. Google says that allowing or denying a multi-region does not imply the same for its sub-locations. Opt-in Regions can also be locked, so account owners cannot turn them on themselves.

"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 access outside approved RegionsAWSService control policies (SCPs)Region and residencydocumented
Deny enabling or disabling opt-in RegionsAWSService control policies (SCPs)Region and residencydocumented
Allowed locations for new resourcesAzureAzure Policy (built-in definitions)Region and residencydocumented
Allowed locations assigned at a management groupAzureManagement group assignmentRegion and residencydocumented
Resource location restrictionGoogle CloudOrganization Policy Service (managed and legacy constraints)Region and residencynone found

What these guardrails break

  • Deny access outside approved Regions (AWS): Global services missing from the exemption list break: the README warns the example might not include all of the latest global AWS services or operations.
  • Deny enabling or disabling opt-in Regions (AWS): Account owners cannot turn opt-in Regions on or off themselves; the README restricts these actions to a privileged role.
  • Allowed locations for new resources (Azure): Deployments to other locations return 403, and the definition itself excludes resource groups, Microsoft.AzureActiveDirectory/b2cDirectories and resources that use the 'global' region.
  • Allowed locations assigned at a management group (Azure): Policy and access assigned at a management group cascade to all child subscriptions, and scopes listed in notScopes on the assignment are skipped entirely: they are not evaluated or included in the compliance count.
  • Resource location restriction (Google Cloud): Google documents that allowing or denying a multi-region does not imply the same for its sub-locations, so a deny of the us multi-region still allows resources in us-east1.

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. Deny access outside approved Regions, read 10 Nov 2026
  2. Deny enabling or disabling opt-in Regions, read 10 Nov 2026
  3. Allowed locations for new resources, read 10 Nov 2026
  4. Allowed locations assigned at a management group, read 10 Nov 2026
  5. Resource location restriction, read 10 Nov 2026

Last reviewed 16 Nov 2026.