Skip to content
Cloud Governance Tools

Restrict load balancer creation based on load balancer types

Restrict load balancer creation based on load balancer types is a Google Cloud guardrail written in organization Policy Service. Limits which types of load balancer can be created in an organization, folder or project. What it breaks: google documents that every load balancer type to be allowed or denied must be listed explicitly, from a fixed list of values.

More resource and cost guardrails ยท About Organization Policy Service

constraints/compute.restrictLoadBalancerCreationForTypes
This list constraint defines the set of load balancer types which can be created for an organization, folder, or project. Every load balancer type to be allowed or denied must be listed explicitly. By default, creation of all types of load balancers is allowed.
The list of allowed or denied values must be identified as the string name of a load balancer, and can only include values from the list below: INTERNAL_TCP_UDP
INTERNAL_HTTP_HTTPS
GLOBAL_INTERNAL_MANAGED_HTTP_HTTPS
GLOBAL_INTERNAL_MANAGED_TCP_PROXY
REGIONAL_INTERNAL_MANAGED_TCP_PROXY
EXTERNAL_NETWORK_TCP_UDP
EXTERNAL_TCP_PROXY
EXTERNAL_SSL_PROXY
EXTERNAL_HTTP_HTTPS
EXTERNAL_MANAGED_HTTP_HTTPS
GLOBAL_EXTERNAL_MANAGED_HTTP_HTTPS
GLOBAL_EXTERNAL_MANAGED_TCP_PROXY
GLOBAL_EXTERNAL_MANAGED_SSL_PROXY
REGIONAL_EXTERNAL_MANAGED_TCP_PROXY
To include all internal or all external load balancer types, use the in: prefix followed by INTERNAL or EXTERNAL. For example, allowing in:INTERNAL will allow all load balancer types from the above list that include INTERNAL. For more information about restricting load balancer types, see https://docs.cloud.google.com/load-balancing/docs/org-policy-constraints.
Supported prefixes: is: , in:
For more information, see Organization policy constraints for Cloud Load Balancing .
Blocks
Limits which types of load balancer can be created in an organization, folder or project. (legacy managed constraint, list.)
Breaks
Google documents that every load balancer type to be allowed or denied must be listed explicitly, from a fixed list of values. (source)
Test before applying
As for every Organization Policy Service guardrail: how to test before enforcing
Mechanism
Organization Policy Service (managed and legacy constraints): Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.
Taken from
provider documentation, provider documentation

What the source says

"This list constraint defines the set of load balancer types which can be created for an organization, folder, or project." (read 10 Nov 2026).

On what it breaks: "Every load balancer type to be allowed or denied must be listed explicitly."

Sources

  1. Restrict load balancer creation based on load balancer types, read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.