This document explains how to migrate your client-to-Apigee (also called "northbound") routing configuration
from a managed instance group (MIG) configuration to a Private Service Connect (PSC) based
configuration.
Configure northbound routing to Apigee endpoints. For this task, follow the steps
under the External routing (PSC) tab under Configure routing in the Apigee CLI provisioning
document.
If you have multiple Apigee instances (a multi-region use case), create corresponding NEGs
for each of the Apigee regions and attach them to the backend service of the load balancer. See
Expanding Apigee to multiple regions.
Test the new global load balancer endpoint.
When testing is complete, switch all of your existing DNS entries to point to the new
load balancer endpoint. Note the following:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-10 UTC."],[[["This guide explains how to migrate client-to-Apigee routing from a managed instance group (MIG) to a Private Service Connect (PSC) based configuration."],["The migration is relevant for those currently using a Global external HTTPS Load Balancer (Classic) with a managed instance group (MIG) for routing traffic to Apigee and want to switch to using PSC."],["Migration involves configuring northbound routing to Apigee endpoints using the Apigee CLI, creating NEGs for multi-region use cases, testing the new load balancer, and switching DNS entries to the new load balancer endpoint."],["Because the global external HTTPS load balancer does not support PSC NEG backends, a new global external HTTPS load balancer needs to be created and have the traffic switched to it."]]],[]]
