The steps described in this hybrid install process are performed with one or more of the following:
Google Cloud console
Apigee hybrid UI
gcloud command line
Environment variables
The steps performed using the command line make use of user-created environment variables. If your
terminal window is disconnected, the environment variables are not saved.
The environment variables used in these procedures are as follows:
The gcloud authorization credentials token expires after 20
minutes. If you don't complete all of the steps within that time, you must get the authorization
credentials again. For example:
On the command line, get your gcloud authentication
credentials using the following command:
An environment provides an isolated context or sandbox for running API proxies.
In a single organization, you can create multiple environments.
If you don't do this, you won't be able to complete the hybrid runtime installation, nor
will you have anywhere to deploy your API proxies to.
Next step
Each of these steps is described in the sections that follow.
[[["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-29 UTC."],[[["\u003cp\u003eThis documentation is for Apigee hybrid version 1.6, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eThe hybrid installation process can be performed using the Google Cloud console, Apigee hybrid UI, or the \u003ccode\u003egcloud\u003c/code\u003e command line.\u003c/p\u003e\n"],["\u003cp\u003eEnvironment variables, essential for command-line operations, are defined for both Linux/MacOS and Windows, and they can be verified using the \u003ccode\u003eecho\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eSetting up the Apigee hybrid UI and Google Cloud services involves creating a Google Cloud account and project, enabling APIs, and creating an organization and environment.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud\u003c/code\u003e authorization credentials token expires after 20 minutes, requiring users to re-authenticate if the steps take longer.\u003c/p\u003e\n"]]],[],null,["# Part 1: Google Cloud services and hybrid UI configuration\n\n| You are currently viewing version 1.6 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\nBefore you begin\n----------------\n\n\nThe steps described in this hybrid install process are performed with one or more of the following:\n\n- Google Cloud console\n- Apigee hybrid UI\n- `gcloud` command line\n\n### Environment variables\n\n\nThe steps performed using the command line make use of user-created environment variables. If your\nterminal window is disconnected, the environment variables are not saved.\n| **Tip:** Create a shell script to quickly set the environment variables.\n\n\nThe environment variables used in these procedures are as follows:\n\n### Linux / MacOS\n\n export PROJECT_ID=\"\u003cvar translate=\"no\"\u003eyour_project_id\u003c/var\u003e\"\n export ORG_NAME=$PROJECT_ID\n export ORG_DISPLAY_NAME=\"\u003cvar translate=\"no\"\u003eorg_friendly_name\u003c/var\u003e\"\n export ORGANIZATION_DESCRIPTION=\"\u003cvar translate=\"no\"\u003eorg_description_text\u003c/var\u003e\"\n export ANALYTICS_REGION=\"\u003cvar translate=\"no\"\u003eanalytics_region\u003c/var\u003e\"\n export RUNTIMETYPE=HYBRID\n export ENV_NAME=\"\u003cvar translate=\"no\"\u003eenvironment_name\u003c/var\u003e\"\n export ENV_DISPLAY_NAME=\"\u003cvar translate=\"no\"\u003eenv_friendly_name\u003c/var\u003e\"\n export ENV_DESCRIPTION=\"\u003cvar translate=\"no\"\u003eenv_description_text\u003c/var\u003e\"\n export DOMAIN=\"\u003cvar translate=\"no\"\u003eexample.com\u003c/var\u003e\"\n export ENV_GROUP=\"\u003cvar translate=\"no\"\u003eenvironment-group-name\u003c/var\u003e\"\n export CLUSTER_NAME=\"\u003cvar translate=\"no\"\u003ecluster_name\u003c/var\u003e\"\n export CLUSTER_LOCATION=\"\u003cvar translate=\"no\"\u003ecluster_region\u003c/var\u003e\"\n\n\nVariable name contents that contain spaces must be enclosed in double quotes. For example: \n\n```\nexport ORGANIZATION_DESCRIPTION=\"My example organization number 1\"\n```\n| **Tip:** Use the `echo $`\u003cvar translate=\"no\"\u003evariable-name\u003c/var\u003e command to verify that the environment variables are properly set.\n\n### Windows\n\n set PROJECT_ID=\"\u003cvar translate=\"no\"\u003eyour_project_id\u003c/var\u003e\"\n set ORG_NAME=$PROJECT_ID\n set ORG_DISPLAY_NAME=\"\u003cvar translate=\"no\"\u003eorg_friendly_name\u003c/var\u003e\"\n set ORGANIZATION_DESCRIPTION=\"\u003cvar translate=\"no\"\u003eorg_description_text\u003c/var\u003e\"\n set ANALYTICS_REGION=\"\u003cvar translate=\"no\"\u003eanalytics_region\u003c/var\u003e\"\n set RUNTIMETYPE=HYBRID\n set ENV_NAME=\"\u003cvar translate=\"no\"\u003eenvironment_name\u003c/var\u003e\"\n set ENV_DISPLAY_NAME=\"\u003cvar translate=\"no\"\u003eenv_friendly_name\u003c/var\u003e\"\n set ENV_DESCRIPTION=\"\u003cvar translate=\"no\"\u003eenv_description_text\u003c/var\u003e\"\n set DOMAIN=\"\u003cvar translate=\"no\"\u003eexample.com\u003c/var\u003e\"\n set ENV_GROUP=\"\u003cvar translate=\"no\"\u003eenvironment-group-name\u003c/var\u003e\"\n set CLUSTER_NAME=\"\u003cvar translate=\"no\"\u003ecluster_name\u003c/var\u003e\"\n set CLUSTER_LOCATION=\"\u003cvar translate=\"no\"\u003ecluster_region\u003c/var\u003e\"\n\n\nVariable name contents that contain spaces must be enclosed in double quotes. For example: \n\n```\nset ORGANIZATION_DESCRIPTION=\"My example organization number 1\"\n```\n| **Tip:** Use the `echo %`\u003cvar translate=\"no\"\u003evariable-name\u003c/var\u003e`%` command to verify that the environment variables are properly set.\n\n#### Authorization credentials token\n\n\nThe `gcloud` authorization credentials token expires after 20\nminutes. If you don't complete all of the steps within that time, you must get the authorization\ncredentials again. For example:\n\nOn the command line, get your `gcloud` authentication\ncredentials using the following command:\n\n### Linux / MacOS\n\n```\nTOKEN=$(gcloud auth print-access-token)\n```\n\n### Windows\n\n```\nfor /f \"tokens=*\" %a in ('gcloud auth print-access-token') do set TOKEN=%a\n```\n\n#### Other environment variables\n\n\nYou will be asked to add more environment variables in the process of this guide, and you may want\nto add them to the script. For example:\n\n- LONG_RUNNING_OPERATION_ID: The UUID of the asynchronous, long-running operation that is part of the org creation process.\n- APIGEECTL_HOME: The path to the directory where you install the `apigeectl` utility.\n\n### Process overview\n\n\nThis section provides an overview of the tasks you must accomplish to set up the hybrid UI\nand Google Cloud services.\n\nThe general process for setting up the Apigee hybrid UI and Google Cloud services is as follows:\n\n| **Note:** 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.\n\nNext step\n---------\n\nEach of these steps is described in the sections that follow.\n\n[Let's Go!](/apigee/docs/hybrid/v1.6/precog-gcpaccount)"]]