Apigee Edge to Apigee X pre-requisite that need to be consider for migration

We are planning for Apigee Edge to Apigee X Migration and what would be the pre-requisites that we need to keep in mind before start downloading the proxies from edge and deploy in X ?

Solved Solved
1 2 416
1 ACCEPTED SOLUTION

Hello!

There are a few concepts that differ from Edge to X but the main structure and functionality is the same, the change is smoother than going from OPDK to Hybrid.

Nevertheless, there are a few changes and a a similar googlecloudcommunity topic that was answered from one of our staff @dchiesa1, you can check it here

  • identity for admin and operator users in Apigee X is governed by GCP IAM and RBAC, not Apigee IAM and RBAC. Roles are GCP roles, not Apigee roles. 
  • the VirtualHost concept is gone, replaced by environment groups and GCP External Load Balancer.
  • There are various new policies in Apigee X: DialogFlow, CORS, DataCapture, ExternalCallout, TraceCapture
  • API Proxy revisions are immutable, once deployed.
  • You can deploy a maximum of 50 proxies to an environment in Apigee X
  • provisioning and setup  of Apigee X is.... up to you.  (In Apigee Edge, the Apigee ops team did all the provisioning)
  • KVMs are all encrypted, using a customer-provided encryption key
  • The Admin API endpoint is different (apigee.googleapis.com), and the authentication is different (need OAuth tokens always)

You can also refer to this documentation table to see more differences.

Hope this helped!

 

View solution in original post

2 REPLIES 2

Hello!

There are a few concepts that differ from Edge to X but the main structure and functionality is the same, the change is smoother than going from OPDK to Hybrid.

Nevertheless, there are a few changes and a a similar googlecloudcommunity topic that was answered from one of our staff @dchiesa1, you can check it here

  • identity for admin and operator users in Apigee X is governed by GCP IAM and RBAC, not Apigee IAM and RBAC. Roles are GCP roles, not Apigee roles. 
  • the VirtualHost concept is gone, replaced by environment groups and GCP External Load Balancer.
  • There are various new policies in Apigee X: DialogFlow, CORS, DataCapture, ExternalCallout, TraceCapture
  • API Proxy revisions are immutable, once deployed.
  • You can deploy a maximum of 50 proxies to an environment in Apigee X
  • provisioning and setup  of Apigee X is.... up to you.  (In Apigee Edge, the Apigee ops team did all the provisioning)
  • KVMs are all encrypted, using a customer-provided encryption key
  • The Admin API endpoint is different (apigee.googleapis.com), and the authentication is different (need OAuth tokens always)

You can also refer to this documentation table to see more differences.

Hope this helped!

 

Thank you @razvanbulzan for the steps and documentation.