Apigee facilita le comunicazioni tra le richieste dell'API client e i servizi Apigee e Cloud
tramite una connessione tra due reti: il VPC (o piano di runtime) Apigee e il
VPC del cliente. Queste due reti sono collegate tra loro tramite
una connessione privata in un processo noto
come peering VPC.
L'esempio seguente mostra come il peering VPC consente la comunicazione tra il VPC Apigee e il
VPC cliente:
Il peering VPC consente al VPC Apigee di elaborare richieste e risposte inviate al VPC cliente:
Traffico in uscita: richieste proxy API inviate dai client al VPC del cliente che vengono
trasmesse al piano di runtime Apigee per l'elaborazione. Anche servizi aggiuntivi come logging,
gestione delle identità e metriche sono accessibili al piano di runtime.
Traffico in uscita: le richieste proxy API che devono accedere alle API di destinazione o ad altri
servizi di backend nel VPC del cliente costituiscono la route in uscita. Questi servizi in uscita
elaborano le risposte prima di restituirle
al VPC del cliente per un'ulteriore elaborazione da parte del runtime Apigee prima che una risposta venga inviata al
client.
Il passaggio di provisioning di Apigee, Configura il servizio di rete, esegue il peering VPC e alloca un intervallo di indirizzi IP (un intervallo CIDR) ad Apigee.
Dimensionamento della rete
Ogni
istanza Apigee richiede un intervallo CIDR non sovrapposto di /22. Al piano di runtime Apigee (noto anche come data plane) vengono assegnati indirizzi IP all'interno dell'intervallo CIDR.
Di conseguenza, è importante che l'intervallo sia riservato ad Apigee e non venga utilizzato da altre
applicazioni nella rete VPC del cliente.
Quando crei un'istanza, hai due opzioni per specificare un intervallo IP di rete:
Alloca automaticamente l'intervallo: quando crei un'istanza Apigee, consenti ad Apigee
di allocare qualsiasi intervallo disponibile e non sovrapposto dall'intervallo più grande allocato a Google.
Ogni volta che viene ricreata un'istanza, l'intervallo IP viene allocato automaticamente. In questi casi, è possibile che la nuova istanza utilizzi un nuovo intervallo IP, se disponibile e non sovrapposto ad altri prodotti o servizi.
Specifica un intervallo IP: puoi specificare l'intervallo IP che verrà utilizzato da Apigee. Questo intervallo IP
deve provenire dall'intervallo non sovrapposto sottoposto a peering con Apigee. Questa opzione è utile quando vuoi allocare un intervallo IP più ampio per più prodotti Cloud,
come Cloud SQL, Cloud Memorystore, Apigee e altri, e vuoi anche poter specificare
intervalli IP effettivi per ciascuno di questi prodotti. Questo intervallo può essere un intervallo IP non RFC 1918, purché non sia un indirizzo IP pubblico utilizzato privatamente (PUPI).
.
Dopo aver creato un'istanza, non puoi modificare l'intervallo CIDR. Per modificare l'intervallo CIDR,
devi eliminare l'istanza e riconfigurarne una nuova. Fai attenzione se hai una sola
istanza in un'organizzazione.
Considerazioni
Prima di allocare intervalli CIDR, consulta la sezione
Considerazioni nella documentazione di Virtual Private Cloud.
Quando crei una connessione di peering con Google, assicurati che gli IP pubblici non vengano
scambiati. Per verificare:
Nei dettagli della connessione di peering, assicurati che l'opzione Scambia route di subnet con IP pubblico sia
impostata su Nessuno, come mostrato nello screenshot seguente.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 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"]]
