[[["容易理解","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-09-05 (世界標準時間)。"],[[["\u003cp\u003eApigee offers two distinct networking options for new organizations: Non-VPC Peering and VPC Peering.\u003c/p\u003e\n"],["\u003cp\u003eNon-VPC Peering utilizes Private Service Connect (PSC) for both northbound (client to Apigee) and southbound (Apigee to target services) traffic, eliminating the need for dedicated IP ranges.\u003c/p\u003e\n"],["\u003cp\u003eVPC Peering uses private service access to create a private connection between your VPC network and Apigee's network and requires dedicated IP range allocation during Apigee instance provisioning.\u003c/p\u003e\n"],["\u003cp\u003eWhile VPC Peering can use both VPC peering and PSC for southbound routing, Non-VPC Peering only uses PSC.\u003c/p\u003e\n"],["\u003cp\u003eNon-VPC peering is exclusively available via the CLI provisioning steps, whereas VPC peering can be set up via the console or CLI, and both can be set up using Terraform.\u003c/p\u003e\n"]]],[],null,["# Apigee networking options\n\nYou can choose one of two distinct networking options when you provision a new Apigee organization:\n[Non-VPC Peering](#non-vpc-peering-architecture-overview) or [VPC peering](#vpc-peering-architecture-overview).\nThese two options are summarized below.\n\n- The Non-VPC Peering option uses [Private Service Connect](/vpc/docs/private-service-connect) (PSC) to route traffic from clients to Apigee (northbound traffic) and from Apigee to target services hosted in your Google Cloud projects (southbound traffic). In this model, you do not need to provide dedicated IP ranges in your network during Apigee provisioning. See also [Southbound networking patterns](/apigee/docs/api-platform/architecture/southbound-networking-patterns-endpoints) and [Northbound networking with Private Service Connect](/apigee/docs/api-platform/system-administration/northbound-networking-psc).\n- The VPC-peering option uses [private service access](/vpc/docs/private-services-access) to create a private connection between your VPC network and a network owned by Apigee. This model employs [VPC network peering](/vpc/docs/vpc-peering) to connect your network with Apigee's. The peering model requires you to allocate dedicated IP ranges in your network when you provision a new instance of Apigee. Additionally, you can also leverage [Private Service Connect](/vpc/docs/private-service-connect) (PSC) to route traffic from clients to Apigee (northbound traffic) and from Apigee to target services hosted in your Google Cloud projects (southbound traffic) along with VPC peering.\n\nNon-VPC Peering option\n----------------------\n\n| **Note:** The non-VPC peering option is available using the CLI provisioning steps only. Non-VPC peering through the Cloud console is not available at this time. You can use the CLI to provision Apigee with non-VPC peering for [subscription](/apigee/docs/api-platform/get-started/install-cli-non-peered), [Pay-as-you-go](/apigee/docs/api-platform/get-started/install-cli-non-peered-paygo), and [eval](/apigee/docs/api-platform/get-started/install-cli-non-peered-eval) organizations.\n|\n| We also support using [Terraform](https://www.terraform.io/) to provision Apigee\n| without VPC peering. The [Apigee terraform modules\n| repository](https://github.com/apigee/terraform-modules/tree/main/samples) on GitHub. provides end-to-end sample\n| modules and reusable terraform modules for Apigee.\n\n\nThis option does not require VPC peering. With this approach, you are not required to provide networks\nand IP ranges during the Apigee provisioning process. Instead, you use\n[Private Service Connect](/vpc/docs/private-service-connect)\n(PSC) for routing northbound traffic (from clients to Apigee) and southbound traffic (from Apigee to to target services running\nin your Google Cloud projects).\n\n\nPSC enables private connection between a service producer (Apigee) and a service consumer\n(one or more other Cloud projects that you control). With non-VPC peering provisioning, requests pass through\neither a global external load balancer or a regional external load balancer to a single point\nof attachment, called a [service attachment](/vpc/docs/private-service-connect#service-attachments) (Figure 1) using PSC.\n\n\nThe non-VPC provisioning steps are described in\n[Provision without VPC peering](/apigee/docs/api-platform/get-started/install-cli-non-peered)\n\n\n**Figure 1.** Apigee architecture without VPC peering. See also [Apigee architecture overview](/apigee/docs/api-platform/architecture/overview).\n\n\nVPC peering option\n------------------\n\n\nTraditionally, Apigee has employed [VPC\nnetwork peering](/vpc/docs/vpc-peering) to enable communication between a virtual private cloud (VPC) network managed\nby you and a VPC network managed by Apigee. This configuration allows bi-directional communication\nbetween the two VPC networks and allows Apigee API proxies to call target services deployed in\nyour VPC. If target applications are in the peered network, Apigee can access their IP addresses and route\nAPI proxy traffic to them.\nSee also [Apigee architecture overview](/apigee/docs/api-platform/architecture/overview).\n\nTo create an Apigee instance, you are required to allocate a pair of IP Address Ranges (a /22 and /28 CIDR range) to Apigee and perform\nthe VPC peering between your network and Apigee's network. Each Apigee instance requires\na non-overlapping CIDR range of /22 and /28. The Apigee runtime plane is assigned IP\naddresses from within this CIDR range. As a result, it's important that the range is\nreserved for Apigee and not used by other applications in your VPC network.\n\nApigee supports peering with only one network; however, many enterprises have multiple\nnetworks where applications and services are deployed. In these cases, you can use PSC to privately connect Apigee to\ntarget services running across VPC networks in addition to the peered network (Figure 2).\nSee [Southbound networking patterns](/apigee/docs/api-platform/architecture/southbound-networking-patterns-endpoints) for more information.\n**Figure 2.** Apigee architecture with VPC peering. For details of this architecture, see [Apigee\narchitecture overview](/apigee/docs/api-platform/architecture/overview).\n\n\nThe steps for provisioning Apigee with VPC peering are covered in\n[Provision\nwith VPC peering](/apigee/docs/api-platform/get-started/install-cli).\n\nHow to choose a networking option\n---------------------------------\n\n\nThe following table describes the features/approaches available with each networking option:"]]
