1. In the Apigee UI, go toManagement > Environments.

   Go to Environments

2. In theEnvironments pane, click+ Create Environment.
3. In theCreate an environment pane, enter the following:

   • Name: The programmatic environment name. TheName can't be changed after it is created.

     The name must contain between 2 and 32 characters which can be lower-case letters, numbers, or hyphens. The name must begin with a letter and cannot end with a hyphen. The name must be different from any other environment name in your organization.

   • Display Name: The name for the environment that is displayed in the UI.
   • Description: Optional. A description of the environment.
   • Instance: Leave theInstance field blank. Instances do not apply to Apigee hybrid installations.
   • Environment group: Leave theEnvironment group field blank for now. You will create an environment group in the next procedure.
   • Deployment type: For most Apigee hybrid installations, select the option to deploy individual API proxies. You can optionally deploy an archive of your API proxy configuration environment. For more information, seeSupported deployment types.Note: The deployment type used with this environment cannot be changed after the environment is created.
4. ClickCreate.

Classic Apigee UI

To access the UI and add an environment, perform the following steps:

1. Open theApigee UI. If this is the first time you are logging in, hybrid displays a consent dialog. If you are prompted to select from more than one account, choose the account that owns the Google Cloud project you are using to install Apigee hybrid. Then clickAllow.

Your browser navigates to the UI main landing page:



2. Ensure that your organization is selected from the organization drop-down list. If it is not selected, select it from the drop-down list, as the following example shows:

   

3. ClickAdmin > Environments > Overview.

   

   TheEnvironments view is displayed, with no environments (yet):

4. Click+Environment.

   TheNew environment dialog is displayed:

   

5. Enter the following information in theNew Environment dialog:
   1. Display name(Required): A friendly name for the environment that is used in the UI. For example, "My First Environment" or "test". Unlike theEnvironment name, theDisplay name can include uppercase and other special characters.
   2. Environment name(Required): The programmatic name for the environment; also known as theenvironment ID.

      For example, "my-environment" or "test".

      Caution: An environment name can contain only lowercase letters, numbers, and hyphens. You cannot use uppercase letters or any other special characters. In addition, theEnvironment name can be up to a maximum of 32 characters long. For example:my-test-env ormy-test-env-42.

      TheDisplay name and theEnvironment name can be different.

   3. Description (Optional): Additional information about the environment that you want to add as a reminder of the purpose of the environment. For example, "Created during initial installation".
6. Keep any other defaults and clickCreate.

   Apigee creates the new environment.

   You now need to create an environment group and add your new environment to the group.

Apigee API

To create an environment with theCreate environments API, perform the following steps:

1. Open a terminal on the device you are using to manage Apigee.

2. On the command line, get yourgcloud authentication credentials using the following command:

   Linux / MacOS

   export TOKEN=$(gcloud auth print-access-token)

   To check that your token was populated, useecho, as the following example shows:

   echo $TOKEN

   This should display your token as an encoded string.

   Windows

   for /f "tokens=*" %a in ('gcloud auth print-access-token') do set TOKEN=%a

   To check that your token was populated, useecho, as the following example shows:

   echo %TOKEN%

   This should display your token as an encoded string.

3. Create the following environment variable:

   Linux / MacOS

   export ENV_NAME="YOUR_ENV_NAME"

   Windows

   set ENV_NAME="YOUR_ENV_NAME"

   Where:

   • ENV_NAME(Required) The environment name can contain lowercase letters, dashes, and numbers and must start with a lowercase letter. This name will be used as the identifier and cannot be changed after creation of the environment.
4. Call the following Apigee API:

   No data residency

   curl -H "Authorization: Bearer$TOKEN" -X POST -H "content-type:application/json"   -d '{    "name": "'"$ENV_NAME"'"  }'   "https://apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

   Data residency

   curl -H "Authorization: Bearer$TOKEN" -X POST -H "content-type:application/json"   -d '{    "name": "'"$ENV_NAME"'"  }'   "https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

   On a successful creation request, the Environments API should respond with a message similar to the following:

   {"name":"organizations/hybrid-example/operations/c2aee040-7e79-4fd4-b0cf-79ca1b7098a8","metadata":{"@type":"type.googleapis.com/google.cloud.apigee.v1.OperationMetadata","operationType":"INSERT","targetResourceName":"organizations/hybrid-example/environments/example-env","state":"IN_PROGRESS"}}

   As thestate property in the response indicates, Apigee has started to create the new environment, so its state isIN_PROGRESS.

5. Check to verify the environment was created successfully:

   No data residency

   curl -H "Authorization: Bearer$TOKEN" \          "https://apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

   Data residency

   curl -H "Authorization: Bearer$TOKEN" \          "https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

   On a successful creation request, the Environments API responds with a message similar to the following:

   [  "your-environment-name"]