You can install Apigee hybrid on a number of platforms, including Anthos on premises, AWS, Bare
Metal, EKS, Google Kubernetes Engine (GKE), OpenShift, and others. For a list of supported platforms
see Apigee hybrid: supported platforms.
Permissions
Each supported platform has its own permission requirements for creating a cluster. As cluster
owner, you can proceed to install the Apigee-specific components (including cert-manager and the
Apigee runtime) into the cluster. However, if you want to delegate to another user the
installation of the runtime components into the cluster, you can manage the necessary permissions
through Kubernetes
authn-authz.
[[["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-08-26 UTC."],[[["\u003cp\u003eApigee hybrid version 1.11 can be installed on various platforms, including Anthos, AWS, Bare Metal, EKS, GKE, and OpenShift.\u003c/p\u003e\n"],["\u003cp\u003eCluster owners can install Apigee components, but permissions for runtime component installation can be delegated using Kubernetes auth.\u003c/p\u003e\n"],["\u003cp\u003eBefore installing the Apigee runtime, users must complete project and organization setup, which includes having a Google Cloud project, billing account, and \u003ccode\u003egcloud\u003c/code\u003e CLI.\u003c/p\u003e\n"],["\u003cp\u003eUsers must also enable APIs, create an Apigee organization, create an environment and group, and choose between Helm or \u003ccode\u003eapigeectl\u003c/code\u003e as the installation tool.\u003c/p\u003e\n"],["\u003cp\u003eIf you want to use Google Cloud Virtual Private Cloud Service Controls with Apigee hybrid, see the dedicated instructions before proceeding.\u003c/p\u003e\n"]]],[],null,["# Part 2: Hybrid runtime setup\n\n| You are currently viewing version 1.11 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nSupported platforms\n-------------------\n\n\nYou can install Apigee hybrid on a number of platforms, including Anthos on premises, AWS, Bare\nMetal, EKS, Google Kubernetes Engine (GKE), OpenShift, and others. For a list of supported platforms\nsee [Apigee hybrid: supported platforms](/apigee/docs/hybrid/supported-platforms).\n\nPermissions\n-----------\n\n\nEach supported platform has its own permission requirements for creating a cluster. As cluster\nowner, you can proceed to install the Apigee-specific components (including cert-manager and the\nApigee runtime) into the cluster. However, if you want to delegate to another user the\ninstallation of the runtime components into the cluster, you can manage the necessary permissions\nthrough Kubernetes\n[authn-authz](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).\n\nFor a complete list of Kubernetes resources and custom resources that are used by Apigee installations,\nsee [Kubernetes and custom resources used by Apigee](../kubernetes-resources).\n\nPrerequisites\n-------------\n\nThis section describes tasks you must accomplish before you begin the runtime plane quickstart\ninstall.\n\n| **Note about VPC Service Controls:** If you plan to enable Google Cloud [Virtual Private Cloud (VPC) Service\n| Controls](https://cloud.google.com/vpc-service-controls) with your Apigee hybrid installation, see [Using VPC Service Controls with Apigee and\n| Apigee hybrid](/apigee/docs/api-platform/security/vpc-sc) for instructions before you proceed."]]
