LinkedIn
Twitter
Introduction
Apigee hybrid is a platform for developing and managing API proxies that features a hybrid deployment model. The hybrid model includes a management plane hosted by Apigee in the Cloud and a runtime plane that you install and manage on one of the supported Kubernetes platforms or on-premise in your data center.
Apigee Hybrid Architecture
Below diagram shows the Apigee hybrid architecture in general.
This allows customers to leverage the flexibility and scalability offered from the kubernetes architecture to scale and manage each of the Apigee hybrid runtime components independently.
Benefits of Hybrid API Management
- Latency - Customers can position the gateway as close to the workload as possible. This is especially true, as when the consumer and the provider of the API are in the same cloud or data center.
- Security; Allows customers to have API data/payloads within customer approved network boundaries.
- Customizability - Customers can set their own TLS ciphers, static IPs, VPNs etc. for the API runtime.
Deploying the Runtime on AWS EKS
This short article provides a github repository which describes how to setup an AWS EKS ( elastic kubernetes service) cluster using terraform with the required resources to enable the installation of the Apigee hybrid runtime on the EKS cluster afterwards.
The terraform configuration defines a new VPC in which to provision the cluster, and uses the public EKS module to create the required resources, including Auto Scaling Groups, security groups, and IAM Roles and Policies.
At the end of the steps to install Apigee hybrid along with the helm charts, the Apigee Runtime components would be created in the AWS EKS cluster as shown below:
Please see the github repository with the terraform code here.