Skip to content
Cloud Governance Tools

Custom organization policy constraints: what it can block and where it stops

Custom organization policy constraints is a Google Cloud mechanism. A custom constraint is defined in a YAML file that names the resources, methods, conditions and actions subject to the constraint. It applies to fields of resource types in services that support custom constraints, in the organization where the constraint is created.

All mechanisms ยท Google Cloud guardrails

A custom constraint is defined in a YAML file that names the resources, methods, conditions and actions subject to the constraint. Conditions are written in Common Expression Language (CEL), and you then enforce the constraint with an organization policy.

A custom constraint is defined in a YAML file that names the resources, methods, conditions and actions subject to the constraint. Conditions are written in Common Expression Language (CEL), and the constraint is then enforced with an organization policy. It applies to fields of resource types in services that support custom constraints.

Limits: most resource types support up to 20 custom constraints, a condition can contain up to 1,500 characters, behavior is specific to each service, and a policy set with set-policy takes up to 15 minutes to take effect. Policy Simulator previews the impact of a new custom constraint, and the policy can first be set in dry-run mode. 1 library entry uses a custom constraint.

Documented limits

  • Most resource types support up to 20 custom constraints. (source)
  • A condition can contain up to 1,500 characters. (source)
  • Behavior and supported parameters are specific to each service. (source)
  • A policy set with set-policy requires up to 15 minutes to take effect. (source)

Testing before enforcement

Policy Simulator for Organization Policy previews the impact of a new custom constraint, and the policy can first be set in dry-run mode with the dryRunSpec update mask. (source)

The 1 library entry written in it

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. Custom organization policy constraints, read 10 Nov 2026
  2. Testing, read 10 Nov 2026

Last reviewed 16 Nov 2026.