VPC 피어링 옵션은 비공개 서비스 액세스를 사용하여 사용자의 VPC 네트워크와 Apigee가 소유한 네트워크 간에 비공개 연결을 만듭니다. 이 모델은 VPC 네트워크 피어링을 사용하여 사용자 네트워크를 Apigee와 연결합니다. 피어링 모델을 사용하려면 Apigee의 새 인스턴스를 프로비저닝할 때 네트워크에 전용 IP 범위를 할당해야 합니다.
또한 VPC 피어링과 함께 Private Service Connect(PSC)를 활용하여 Northbound 트래픽(클라이언트에서 Apigee로) 및 Southbound 트래픽(Apigee에서 Google Cloud 프로젝트에서 호스팅되는 대상 서비스로)을 라우팅할 수도 있습니다.
비VPC 피어링 옵션
이 옵션은 VPC 피어링이 필요하지 않습니다. 이 접근 방식을 사용하면 Apigee 프로비저닝 프로세스 중에 네트워크와 IP 범위를 제공할 필요가 없습니다. 대신 Private Service Connect(PSC)를 사용하여 Northbound 트래픽(클라이언트에서 Apigee로) 및 Southbound 트래픽(Apigee에서 Google Cloud 프로젝트에서 실행 중인 대상 서비스로)을 라우팅합니다.
PSC를 사용하면 서비스 프로듀서(Apigee)와 서비스 소비자(제어하는 하나 이상의 다른 Cloud 프로젝트) 간의 비공개 연결이 가능합니다. 비VPC 피어링 프로비저닝을 사용하면 요청이 PSC를 사용하여 전역 외부 부하 분산기 또는 리전 외부 부하 분산기를 통해 서비스 연결이라는 단일 연결 지점으로 전달됩니다(그림 1).
그림 1. VPC 피어링이 없는 Apigee 아키텍처입니다. Apigee 아키텍처 개요도 참조하세요.
VPC 피어링 옵션
기존에는 Apigee에서 VPC 네트워크 피어링을 사용하여 사용자가 관리하는 가상 프라이빗 클라우드(VPC) 네트워크와 Apigee에서 관리하는 VPC 네트워크 간의 통신을 사용 설정했습니다. 이 구성을 사용하면 두 VPC 네트워크 간의 양방향 통신이 허용되며 Apigee API 프록시가 VPC에 배포된 대상 서비스를 호출할 수 있습니다. 대상 애플리케이션은 피어링된 네트워크에 있는 경우 Apigee는 해당 IP 주소에 액세스하고 API 프록시 트래픽을 IP 주소로 라우팅할 수 있습니다.
Apigee 아키텍처 개요도 참조하세요.
Apigee 인스턴스를 만들려면 IP 주소 범위 쌍(/22 및 /28 CIDR 범위)을 Apigee에 할당하고 네트워크와 Apigee 네트워크 간에 VPC 피어링을 수행해야 합니다. 각 Apigee 인스턴스에는 /22 및 /28의 중첩되지 않는 CIDR 범위가 필요합니다. Apigee 런타임 영역에는 이 CIDR 범위 내의 IP 주소가 할당됩니다. 따라서 이 범위는 Apigee에 예약되어야 하며 VPC 네트워크의 다른 애플리케이션에서 사용하면 안 됩니다.
Apigee는 하나의 네트워크와만 피어링을 지원합니다. 하지만 많은 기업이 애플리케이션과 서비스가 배포되는 네트워크 여러 개를 가집니다. 이러한 경우 PSC를 사용하여 피어링된 네트워크 외에도 VPC 네트워크에서 실행되는 대상 서비스에 Apigee를 비공개로 연결할 수 있습니다(그림 2).
자세한 내용은 Southbound 네트워킹 패턴을 참조하세요.
그림 2. VPC 피어링을 사용하는 Apigee 아키텍처입니다. 이 아키텍처에 대한 자세한 내용은 Apigee 아키텍처 개요를 참조하세요.
[[["이해하기 쉬움","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(UTC)"],[[["\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:"]]
