自動分配 IP 範圍: 如果您希望 Google Cloud 為您管理 IP 範圍,請選擇這個選項。系統會分配兩個範圍,一個長度為 /22,另一個長度為 /28。
範圍名稱如下:google-managed-services-NETWORK_NAME-PREFIX_LENGTH。如需更多資訊和重要注意事項,請參閱「瞭解對等互連範圍」。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-21 (世界標準時間)。"],[[["\u003cp\u003eThis guide explains how to configure Service Networking for Apigee, focusing on setting up private connectivity via VPC Network Peering between your network and Apigee, excluding Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eYou can select from several options for your Authorized network, including the default VPC network, but Google recommends using a custom VPC for production environments instead.\u003c/p\u003e\n"],["\u003cp\u003eWhen allocating peering ranges, you can choose between automatic allocation by Google Cloud or manually selecting existing or creating new IP ranges.\u003c/p\u003e\n"],["\u003cp\u003eThe runtime IP range can be set to automatic, where Apigee will choose an available CIDR range, or custom, where you define a specific IP range with a /22 prefix size.\u003c/p\u003e\n"],["\u003cp\u003eOnce the network configuration is set up and Apigee provisioning is completed, you cannot modify the networking service settings.\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 connectivity setup (using VPC Network Peering)\nbetween your network, Apigee, and Cloud services. For more information on VPC peering with Apigee, see [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 and their pre-selected default values.\nTo view or edit any of the configuration choices, click create **Edit** to open the **Set up networking** panel.\n\nYou can accept the default configuration or select the following options:\n\n1. In the **Authorized network** dropdown, 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 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\n | sizing](/apigee/docs/api-platform/system-administration/peering-ranges#sizing).\n - An existing VPC network in your Cloud project. The drop-down list includes all VPC networks in your Cloud project, even custom ones\n without peering connections. If you select a network that does not have a connection set up yet, you'll be prompted\n 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 dropdown 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** dropdown 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 range Apigee should use.\n\n Enter the custom IP range, which must have a prefix size of /22. The\n range must be available as part of a private connection between your project and Apigee.\n4. Click **Allocate and connect** .\n\n Apigee configures the connection between the VPC and 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 3: Configure hosting and encryption](./console-configure-hosting)."]]