This page applies to Apigee, but not to Apigee hybrid.
View
Apigee Edge documentation.
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.
Overview
If you are currently using the managed instance group (MIG) based configuration using a Global external HTTPS Load Balancer (Classic) for routing external traffic to Apigee, you can choose to migrate this "northbound" traffic to use a PSC based configuration.
Migration steps
- 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: