Apigee memfasilitasi komunikasi antara permintaan API klien dan layanan Apigee dan Cloud
melalui koneksi antara dua jaringan: VPC Apigee (atau runtime plane) dan
VPC Pelanggan. Kedua jaringan ini diikat bersama menggunakan
koneksi pribadi dalam proses yang dikenal
sebagai peering VPC.
Contoh berikut menunjukkan cara peering VPC memungkinkan komunikasi antara VPC Apigee dan VPC Pelanggan:
Peering VPC memungkinkan VPC Apigee memproses permintaan dan respons yang dikirim ke VPC Pelanggan:
Traffic ke utara: Permintaan proxy API yang dikirim dari klien ke VPC Pelanggan yang
diteruskan ke bidang runtime Apigee untuk diproses. Layanan tambahan seperti logging, pengelolaan identitas, dan metrik juga dapat diakses oleh bidang runtime.
Traffic ke hilir: Permintaan proxy API yang harus mengakses API target atau layanan backend lainnya di VPC Pelanggan merupakan rute ke hilir. Layanan southbound ini
memproses respons sebelum menampilkannya
ke VPC Pelanggan untuk diproses lebih lanjut oleh runtime Apigee sebelum respons dikirim ke
klien.
Langkah penyediaan Apigee, Konfigurasi Service Networking, melakukan
peering VPC dan mengalokasikan Rentang Alamat IP (rentang CIDR) ke Apigee.
Penentuan ukuran jaringan
Setiap
instance Apigee memerlukan rentang CIDR /22 yang tidak tumpang-tindih. Bidang runtime Apigee (alias bidang data) diberi alamat IP dari dalam rentang CIDR.
Oleh karena itu, rentang tersebut harus dicadangkan untuk Apigee dan tidak digunakan oleh aplikasi lain di jaringan VPC pelanggan.
Saat membuat instance, ada dua opsi untuk menentukan rentang IP jaringan:
Alokasikan rentang secara otomatis - Saat Anda membuat instance Apigee, izinkan Apigee
untuk mengalokasikan rentang yang tersedia dan tidak tumpang-tindih dari rentang yang lebih besar yang dialokasikan ke Google.
Setiap kali instance dibuat ulang, rentang IP akan dialokasikan secara otomatis. Dalam kasus tersebut, instance baru mungkin menggunakan rentang IP baru, jika tersedia dan tidak tumpang-tindih dengan produk atau layanan lain.
Tentukan rentang IP - Anda dapat menentukan rentang IP yang akan digunakan Apigee. Rentang IP ini harus berasal dari rentang yang tidak tumpang-tindih yang di-peering dengan Apigee. Opsi ini berguna jika Anda ingin mengalokasikan rentang IP yang lebih besar untuk beberapa produk Cloud,
seperti Cloud SQL, Cloud Memorystore, Apigee, dan lainnya, dan Anda juga ingin dapat menentukan
rentang IP aktual untuk setiap produk ini. Rentang ini dapat berupa rentang IP non-RFC 1918 selama rentang tersebut bukan alamat IP publik yang digunakan secara pribadi (PUPI).
.
Setelah membuat instance, Anda tidak dapat mengubah rentang CIDR. Untuk mengubah rentang CIDR, Anda harus menghapus instance dan mengonfigurasi ulang instance baru. Berhati-hatilah jika Anda hanya memiliki satu instance dalam organisasi.
Pertimbangan
Sebelum mengalokasikan rentang CIDR, lihat
Pertimbangan dalam dokumentasi Virtual Private Cloud.
Saat membuat koneksi peering dengan Google, pastikan IP publik tidak
dipertukarkan. Untuk memeriksa:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eThis content focuses on Apigee (not Apigee hybrid) and its network connectivity through VPC peering, which links the Apigee runtime plane and Customer VPC.\u003c/p\u003e\n"],["\u003cp\u003eVPC peering facilitates both northbound (client to Apigee) and southbound (Apigee to backend services) traffic flow between the Apigee VPC and the Customer VPC.\u003c/p\u003e\n"],["\u003cp\u003eEach Apigee instance requires a unique /22 CIDR range for its runtime plane, along with an additional non-overlapping /28 CIDR range for troubleshooting access.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an instance, you can either let Apigee auto-allocate the IP range or specify a custom, non-overlapping range, but this range cannot be modified after the instance is created.\u003c/p\u003e\n"],["\u003cp\u003eIt is crucial to ensure that public IPs are not exchanged when creating a peering connection with Google to avoid potential IP conflicts, as Apigee uses privately used public IP addresses (PUPI).\u003c/p\u003e\n"]]],[],null,["# Understanding peering ranges\n\n*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\n| **Important:** This topic only applies to organizations that were created with VPC peering enabled. See also [Apigee networking options](/apigee/docs/api-platform/get-started/networking-options).\n\nApigee facilitates communications between client API requests and Apigee and Cloud services\nthrough a connection between two networks: the Apigee (or *runtime plane* ) and the\nCustomer VPC. These two networks are tethered together using\n[a private connection](/vpc/docs/configure-private-services-access) in a process known\nas *VPC peering*.\n\nThe following example shows how VPC peering enables communication between the Apigee VPC and the\nCustomer VPC:\n\nVPC peering enables the Apigee VPC to process requests and responses sent to the Customer\nVPC:\n\n- **Northbound traffic:** API proxy requests sent from clients to the Customer VPC that are\n passed through to the Apigee runtime plane for processing. Additional services such as logging,\n identity management, and metrics are also accessible to the runtime plane.\n\n- **Southbound traffic:** API proxy requests that must access target APIs or other\n backend services on the Customer VPC constitute the southbound route. These southbound services\n process the responses before returning them\n to the Customer VPC for further processing by the Apigee runtime before a response is sent to the\n client.\n\n\nThe Apigee provisioning step, [Configure service networking](/apigee/docs/api-platform/get-started/install-cli#service-networking), performs the\nVPC peering and allocates an IP Address Range (a CIDR range) to Apigee.\n\nNetwork sizing\n--------------\n\nEach [Apigee instance](/apigee/docs/api-platform/system-administration/instances) requires a non-overlapping CIDR range of /22. The Apigee\nruntime plane (aka data plane) is assigned IP addresses from within the CIDR range.\nAs a result, it's important that the range is reserved for Apigee and not used by other\napplications in the customer VPC network.\n| **Note:** In addition to the /22 range that is created, Apigee requires a non-overlapping, available /28 CIDR range. This /28 range is used by Apigee to access the instance for troubleshooting purposes and cannot be customized or changed. See also [Creating instances](/apigee/docs/api-platform/system-administration/instances).\n\n\nAn instance is created when:\n\n1. An Apigee organization is first provisioned, either through the [UI wizard](/apigee/docs/api-platform/get-started/overview) or the [command-line interface](/apigee/docs/api-platform/get-started/install-cli) (CLI).\n2. When expanding Apigee to a new Cloud region for an existing organization. See also [Expanding Apigee to multiple regions](/apigee/docs/api-platform/system-administration/multi-region).\n\n| **Note:**You must have the role of Apigee Organization Admin or Apigee Operator to create an instance.\n\n\nWhen you create an instance, there are two options for specifying a network IP range:\n\n- **Auto-allocate the range** - When you create an Apigee instance, allow Apigee to allocate any available, non-overlapping range from the larger range allocated to Google. Each time an instance is re-created, the IP range is auto-allocated. In such cases, it is possible that the new instance may use a new IP range, if one is available and is non-overlapping with other products or services.\n- **Specify an IP range** - You can specify the IP range that Apigee will use. This IP range must be from the non-overlapping range that is peered with Apigee. This option is useful when you want to allocate a larger IP range for multiple Cloud products, such as Cloud SQL, Cloud Memorystore, Apigee, and others, and you also want to be able to specify actual IP ranges for each of these products. This range could be a non-RFC 1918 IP range as long as the range is not a privately used public IP address (PUPI)). .\n\n\nAfter you create an instance, you *cannot* change the CIDR range. To change the CIDR range,\nyou must delete the instance and reconfigure a new one. Be careful if you have only one\ninstance in an organization.\n\nConsiderations\n--------------\n\n\nBefore allocating CIDR ranges, refer to\n[Considerations](https://cloud.google.com/vpc/docs/configure-private-services-access#considerations) in the Virtual Private Cloud documentation.\n\n\nWhen creating a peering connection with Google, ensure that public IPs are not\nexchanged. To check:\n\n1. In the Google Cloud console, go to the **VPC Network Peering** page. See also [Using VPC Network Peering](https://cloud.google.com/vpc/docs/using-vpc-peering#console_1).\n\n [Go to VPC network peering](https://console.cloud.google.com/networking/peering/list?_ga=2.60789677.1018243021.1642011235-1753111617.1642011235)\n2. Select your VPC network peering connection.\n3. In the Peering connection details, make sure that **Exchange subnet routes with public IP** is set to **None** , as shown in the following screenshot.\n\n | **Note:** Apigee uses *privately used public IP* (PUPI) addresses, so setting **Exchange subnet routes with public IP** to something other than **None** could potentially cause an IP conflict.\n\n*[VPC]: Virtual Private Cloud"]]
