In this step, you configure Service Networking, which automates the private
connectivity setup (using VPC Network Peering)
between your network, Apigee, and Google Cloud services.
For more information on VPC peering with Apigee, see
Understanding peering ranges.
Perform the step
Permissions required for this task
You can give the Apigee provisioner a predefined role that includes the permissions needed to complete this task,
or give more fine-grained permissions to provide the least privilege necessary.
See Predefined roles
and Service networking permissions.
In Step 2, the console displays a list of networking configuration options
and their pre-selected default values. To view or edit any of the
configuration choices, click createEdit to open the
Set up networking panel.
You can accept the default configuration or select the following options:
In the Authorized network drop-down, select one of the following
to use for peering connections with your Apigee instance:
The default
VPC network created for all Google Cloud projects.
An existing VPC network in your Google Cloud project.
The drop-down list includes all VPC networks in your Google Cloud
project, even custom ones without peering connections. If you select
a network that does not have a connection set up yet, you'll be
prompted to allocate a peering range.
If prompted, choose one of these options in the
Allocated peering ranges section:
Automatically allocate IP range: Choose this option if you
want Google Cloud to manage the IP range for you. Two ranges are
allocated, one of length /22 and one of length /28.
The ranges are named as follows:
google-managed-services-NETWORK_NAME-PREFIX_LENGTH.
For more information and important considerations, see
Understanding peering ranges.
Select one or more existing IP ranges or create a new one:
Choose this option if you want to select the IP range yourself.
From the Select or create an IP range drop-down menu,
select a /21 CIDR range.
If no IP ranges are available, click Allocate a new IP range.
Enter the IP range name in the available field.
Enter the allocated IP address range in the available
field. The range must be able to hold a /21 CIDR length.
In the Select runtime IP range section, choose one of these
options:
Automatic (Recommended): Apigee automatically selects an
available CIDR range with a prefix size of /22. No further action
on your part is required.
Custom: Select this option if you want to specify which
IP ranges Apigee should use.
Enter the custom IP ranges, one with a prefix size of /22,
and one with a prefix size of /28.
The ranges must be available as part of a private connection
between your project and Apigee.
Click Allocate and connect.
Apigee configures the connection between the VPC and
Google's services to use IP addresses within
the allowed ranges. This operation may take a few minutes to complete.
Once the service networking options are configured as desired, click
Next.
[[["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-08-26 UTC."],[[["\u003cp\u003eThis guide explains how to configure Service Networking for Apigee, which establishes private connectivity via VPC Network Peering between your network, Apigee, and other Google Cloud services.\u003c/p\u003e\n"],["\u003cp\u003eYou can select either a default or an existing custom VPC network for peering with your Apigee instance, and the usage of the default is discouraged for production environments.\u003c/p\u003e\n"],["\u003cp\u003eWhen setting up allocated peering ranges, you can choose to have Google Cloud automatically manage the IP ranges or select/create specific IP ranges yourself, with recommendations against the automatic option for dynamic routes.\u003c/p\u003e\n"],["\u003cp\u003eFor the runtime IP range, you can opt for automatic selection of a suitable CIDR range by Apigee or specify custom IP ranges, both of which require a /22 and a /28 prefix size.\u003c/p\u003e\n"],["\u003cp\u003eAfter completing the networking configuration and moving past Step 4, you will not be able to modify these network settings, as Apigee doesn't support changes to the network configuration post-provisioning.\u003c/p\u003e\n"]]],[],null,["*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nWhat you're doing in this step\n\nIn this step, you configure Service Networking, which automates the private\nconnectivity setup (using VPC Network Peering)\nbetween your network, Apigee, and Google Cloud services.\nFor more information on VPC peering with Apigee, see\n[Understanding peering ranges](/apigee/docs/api-platform/system-administration/peering-ranges).\n\nPerform the step\n\nPermissions required for this task\n\nYou can give the Apigee provisioner a predefined role that includes the permissions needed to complete this task,\nor give more fine-grained permissions to provide the least privilege necessary.\nSee [Predefined roles](/apigee/docs/api-platform/get-started/permissions#predefined-roles)\nand [Service networking permissions](/apigee/docs/api-platform/get-started/permissions#service-networking-permissions).\n\nIn Step 2, the console displays a list of networking configuration options\nand their pre-selected default values. To view or edit any of the\nconfiguration choices, click create **Edit** to open the\n**Set up networking** panel.\n\nYou can accept the default configuration or select the following options:\n\n1. In the **Authorized network** drop-down, select one of the following to use for peering connections with your Apigee instance:\n - The [default](/vpc/docs/vpc#default-network) VPC network created for all Google Cloud projects. **Note:** Google recommends that you not use \"default\" in a production environment. Instead, we recommend that you create a custom VPC for your Apigee account and connect to that. For information about Apigee's peering network requirements, see [Network sizing](/apigee/docs/api-platform/system-administration/peering-ranges#sizing).\n - An existing VPC network in your Google Cloud project. The drop-down list includes all VPC networks in your Google Cloud\n project, even custom ones without peering connections. If you select\n a network that does not have a connection set up yet, you'll be\n prompted to allocate a peering range.\n\n | **Note:** If your project uses Shared Virtual Private Cloud (VPC) networking, you can select the shared network that will be used to peer with Apigee. If you do not see the network in the drop-down list, be sure you have the required permissions. See [Permissions required for this task](#permissionsrequired).\n2. If prompted, choose one of these options in the **Allocated peering ranges** section:\n - **Automatically allocate IP range:** Choose this option if you want Google Cloud to manage the IP range for you. Two ranges are allocated, one of length /22 and one of length /28. The ranges are named as follows: `google-managed-services-`\u003cvar translate=\"no\"\u003eNETWORK_NAME\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003ePREFIX_LENGTH\u003c/var\u003e. For more information and important considerations, see [Understanding peering ranges](/apigee/docs/api-platform/system-administration/peering-ranges). **Note:**We do not recommend this option if you are using dynamic routes (such as Cloud Router) or a network from a host project.\n - **Select one or more existing IP ranges or create a new one:** Choose this option if you want to select the IP range yourself.\n - From the **Select or create an IP range** drop-down menu, select a /21 CIDR range.\n - If no IP ranges are available, click **Allocate a new IP range** .\n - Enter the **IP range name** in the available field.\n - Enter the **allocated IP address range** in the available field. The range must be able to hold a /21 CIDR length.\n\n | **Note:** If you want to select or allocate an IP range smaller than a /21 CIDR range, you can use the command-line interface, as explained in [Step 4: Configure service networking](/apigee/docs/api-platform/get-started/install-cli#service-networking).\n3. In the **Select runtime IP range** section, choose one of these options:\n - **Automatic (Recommended):** Apigee automatically selects an available CIDR range with a prefix size of /22. No further action on your part is required.\n - **Custom:** Select this option if you want to specify which IP ranges Apigee should use.\n\n Enter the custom IP ranges, one with a prefix size of /22,\n and one with a prefix size of /28.\n The ranges must be available as part of a private connection\n between your project and Apigee.\n4. Click **Allocate and connect** .\n\n Apigee configures the connection between the VPC and\n Google's services to use IP addresses within\n the allowed ranges. This operation may take a few minutes to complete.\n5. Once the service networking options are configured as desired, click **Next** . **Caution:** When you submit the completed configuration for provisioning Apigee (at the end of **Step 4**), you cannot go back and change the network service configuration. Apigee does not support updating or changing the network configuration once provisioning is complete.\n\nGo to the next step, [Step 4: Configure hosting and encryption](./console-configure-hosting)."]]