On September 15, 2026, all Cloud Composer 1 versions and versions 2.0.x of Cloud Composer 2 will reach their planned end of life. You will not be able to use environments with these versions. We recommend planning migration to Cloud Composer 3. Cloud Composer 2 versions 2.1.x and later are still supported and are not impacted by this change.
Cloud Composer and GKE services use VPC peerings to
establish connections between the
components of Cloud Composer environments
(Customer Project and Tenant Project) and between a GKE
cluster and a GKE Control Plane.
If your project has a large-scale network configuration, such as one with
hundreds of networks and many VPC peerings configured, then when you try to
create new Cloud Composer environments, the operations might fail
because of VPC, subnet or forwarding rules quota errors.
The errors that you might encounter are:
The maximum number of VPC peerings per single VPC network is reached.
The default quota for a number of VPC peerings within a single VPC is 25
(unless you request an increase of this quota).
The maximum number of primary and secondary subnet IP ranges is reached.
The quota for this parameter is 400.
The maximum number of forwarding rules in the peering group for Internal TCP/
UDP Load Balancing is reached.
The quota for this parameter is 175.
For more information about default quotas for VPCs in Google Cloud, see
Quotas and limits.
About large-scale networks for Cloud Composer environments
To overcome challenges related to these limits, you can organize your
Cloud Composer environments into several VPC networks connected to
your main/backbone VPC as it is described in the following sections.
This solution is applicable to Shared VPC and non-Shared VPC scenarios.
Large-scale network setup in a non-Shared VPC scenario
To create a large-scale network setup for Cloud Composer:
Create a backbone VPC network.
This network acts as a hub for individual VPC networks that host
Cloud Composer environments.
Create dedicated VPC networks for
Cloud Composer environments. You can combine several
Cloud Composer environments into one VPC network. For example,
you can name these networks composer-vpc-1, composer-vpc-2, and so on.
Establish connectivity between Cloud Composer environment VPC
networks and the backbone VPC by
creating HA VPN tunnels.
Large-scale network setup in a Shared VPC scenario
To solve the network peering limits issue in a Shared VPC networks, organize
your Cloud Composer environments into several projects and VPC
networks connected to one backbone VPC.
To create a large-scale Shared VPC network setup for Cloud Composer:
In the host project,
create a backbone VPC network.
This network connects individual VPC networks for service projects running
Cloud Composer environments.
In the host project,
create VPC networks
for Cloud Composer environments. For example, you can name these
networks composer-shared-vpc-1, composer-shared-vpc-2, and so on.
Establish connectivity between these VPC networks and the backbone VPC
network by manually
creating HA VPN tunnels.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-05 UTC."],[[["\u003cp\u003eThis document provides guidance on organizing large-scale networks for Cloud Composer environments, specifically addressing limitations related to VPC peering quotas.\u003c/p\u003e\n"],["\u003cp\u003ePrivate Service Connect (PSC) is recommended over VPC peering for Cloud Composer 2 environments, as it avoids VPC peering quotas.\u003c/p\u003e\n"],["\u003cp\u003eFor large-scale networks, Cloud Composer environments should be organized into several VPC networks connected to a central backbone VPC network to manage VPC peering, subnet, and forwarding rule quotas.\u003c/p\u003e\n"],["\u003cp\u003eBoth non-Shared VPC and Shared VPC scenarios are addressed, with specific steps for setting up large-scale networks using a backbone VPC and dedicated VPC networks for Cloud Composer environments.\u003c/p\u003e\n"],["\u003cp\u003eHA VPN tunnels are recommended to establish connectivity between Cloud Composer environment VPC networks and the backbone network, ensuring there is no direct peering that could result in overreach on quotas.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nCloud Composer 3 \\| **Cloud Composer 2** \\| [Cloud Composer 1](/composer/docs/composer-1/configure-large-scale-networks \"View this page for Cloud Composer 1\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis section explains how to organize large-scale networks for\nCloud Composer environments.\n\nUse Private Service Connect instead of VPC peering networking **Important:** This guide applies only to environments that use VPC peerings. PSC is the default connectivity type for environments in Cloud Composer 2 (when you create an environment in Google Cloud console), and it does not use VPC peering quotas (your environment's cluster still [uses VPC quotas](/composer/docs/composer-2/configure-private-ip#requirements)).\n\nFor more information, see\n[Configure Private Service Connect](/composer/docs/composer-2/configure-private-service-connect).\n\nQuotas for VPC, subnet and forwarding rules\n\nCloud Composer and GKE services use VPC peerings to\nestablish connections between the\n[components of Cloud Composer environments](/composer/docs/composer-2/environment-architecture)\n(Customer Project and Tenant Project) and between a GKE\ncluster and a GKE Control Plane.\n\nIf your project has a large-scale network configuration, such as one with\nhundreds of networks and many VPC peerings configured, then when you try to\ncreate new Cloud Composer environments, the operations might fail\nbecause of VPC, subnet or forwarding rules quota errors.\n\nThe errors that you might encounter are:\n\n- The maximum number of VPC peerings per single VPC network is reached.\n\n The default quota for a number of VPC peerings within a single VPC is 25\n (unless you request an increase of this quota).\n- The maximum number of primary and secondary subnet IP ranges is reached.\n\n The quota for this parameter is 400.\n- The maximum number of forwarding rules in the peering group for Internal TCP/\n UDP Load Balancing is reached.\n\n The quota for this parameter is 175.\n\nFor more information about default quotas for VPCs in Google Cloud, see\n[Quotas and limits](/vpc/docs/quota#vpc-peering).\n\nAbout large-scale networks for Cloud Composer environments\n\nTo overcome challenges related to these limits, you can organize your\nCloud Composer environments into several VPC networks connected to\nyour main/backbone VPC as it is described in the following sections.\n\nThis solution is applicable to Shared VPC and non-Shared VPC scenarios.\n\nLarge-scale network setup in a non-Shared VPC scenario\n\nTo create a large-scale network setup for Cloud Composer:\n\n1. [Create a backbone VPC network](/vpc/docs/create-modify-vpc-networks#create-custom-network).\n This network acts as a hub for individual VPC networks that host\n Cloud Composer environments.\n\n2. [Create dedicated VPC networks](/vpc/docs/create-modify-vpc-networks#create-custom-network) for\n Cloud Composer environments. You can combine several\n Cloud Composer environments into one VPC network. For example,\n you can name these networks `composer-vpc-1`, `composer-vpc-2`, and so on.\n\n3. Establish connectivity between Cloud Composer environment VPC\n networks and the backbone VPC by\n [creating HA VPN tunnels](/network-connectivity/docs/vpn/how-to).\n\n| **Note:** The recommended way of configuring VPC network is to use custom mode when creating subnets.\n\nLarge-scale network setup in a Shared VPC scenario\n\nTo solve the network peering limits issue in a Shared VPC networks, organize\nyour Cloud Composer environments into several projects and VPC\nnetworks connected to one backbone VPC.\n\nTo create a large-scale Shared VPC network setup for Cloud Composer:\n\n1. In the host project,\n [create a backbone VPC network](/vpc/docs/create-modify-vpc-networks#create-custom-network).\n This network connects individual VPC networks for service projects running\n Cloud Composer environments.\n\n2. In the host project,\n [create VPC networks](/vpc/docs/create-modify-vpc-networks#create-custom-network)\n for Cloud Composer environments. For example, you can name these\n networks `composer-shared-vpc-1`, `composer-shared-vpc-2`, and so on.\n\n3. Establish connectivity between these VPC networks and the backbone VPC\n network by manually\n [creating HA VPN tunnels](/network-connectivity/docs/vpn/how-to).\n\n4. Configure Cloud Composer environments\n [in the Shared VPC setup](/composer/docs/composer-2/configure-shared-vpc).\n\n| **Note:** The recommended way of configuring VPC network is to use custom mode when creating subnets.\n\nWhat's next\n\n- [Configure Shared VPC](/composer/docs/composer-2/configure-shared-vpc)\n- [Create an environment](/composer/docs/composer-2/create-environments)"]]
