Restrict VPC peering usage
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Restrict VPC peering usage is a Google Cloud guardrail written in organization Policy Service. Limits which VPC networks can be peered with the networks of a project, folder or organization. What it breaks: google documents that each peering end is required to have peering permission, so both sides must allow the peer.
More network perimeter guardrails ยท About Organization Policy Service
constraints/compute.restrictVpcPeering
This list constraint defines the set of VPC networks that are allowed to be peered with the VPC networks belonging to this project, folder, or organization. Each peering end is required to have peering permission. By default, a Network Admin for one network can peer with any other network. The allowed/denied list of networks must be identified in the form: under:organizations/ ORGANIZATION_ID , under:folders/ FOLDER_ID , under:projects/ PROJECT_ID , or projects/ PROJECT_ID /global/networks/ NETWORK_NAME .
Supported prefixes: is: , under:
- Blocks
- Limits which VPC networks can be peered with the networks of a project, folder or organization. (legacy managed constraint, list.)
- Breaks
- Google documents that each peering end is required to have peering permission, so both sides must allow the peer. (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 VPC networks that are allowed to be peered with the VPC networks belonging to this project, folder, or organization." (read 10 Nov 2026).
On what it breaks: "Each peering end is required to have peering permission."
Related guardrails
- Prevent creating or expanding public connectivity for VPCsAWS, Service control policies (SCPs), network perimeter
- Block internet gateway ingress for VPCs (declarative policy)AWS, Declarative policies, network perimeter
- Network interfaces should disable IP forwardingAzure, Azure Policy (built-in definitions), network perimeter
- Skip default network creationGoogle Cloud, Organization Policy Service (managed and legacy constraints), network perimeter
Related pages
Sources
- Restrict VPC peering usage, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.