In my initial investigation, I found a valuable GCP reference document offering comprehensive insights into the migration process. This document effectively covers various aspects such as functional and non-functional requirements, standard compliance, etc.
Apigee Sackmesser is a collection of tools that provide a unifying experience, and let you deploy API proxies, shared flows, and configuration to both stacks without writing any additional manifest files.
While there are multiple tools that exist for migrating APIs from different API management platforms to APIGEE, I have not come across a specific migration tool for transferring Self-hosted APIs from Compute Engine to APIGEE X. However, this article provides guidance on the necessary steps you can take to accomplish this migration successfully.
Here are a few suggestions:
- What are the current API authentication and authorization mechanisms in place on the existing platform? Let’s explore the potential for transitioning to a new model that enhances security, rather than simply considering a lift-and-shift approach. Whenever there is an opportunity, it’s important to prioritize improving security models. Here is a Reference link to the Apigee security policy.
- Perform an assessment of your existing APIs, assign scores to each API, and focus on enhancing their security measures to mitigate any potential API threats. By implementing stronger security protocols, you can safeguard your APIs from potential vulnerabilities.
- Begin by establishing basic naming standards for APIs, policies, and other relevant components. Then, consider identifying key reusable components such as security measures, threat protection mechanisms, logging practices, and error-handling techniques. These components can be incorporated as part of shared flows, enabling efficient and consistent implementation across multiple APIs.
- After defining the essential shared flows, design an optimal template encompassing all the foundational components. This template should incorporate different policies available for a given proxy, allowing different developers to reuse and share it. Developers can efficiently leverage base components by establishing a comprehensive and reusable template while ensuring consistency across the API development process.
- Implement a masking or encryption approach to safeguard sensitive data such as Personally Identifiable Information (PII) and Payment Card Industry (PCI) data.
- Consider CI/CD approach to deploying APIs.
- Explore Analytics will help to improve your APIs through analytics.
- Conduct tuning exercises to optimize performance and enhance efficiency.
Here are some additional helpful links: