> [!CAUTION]
> You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.2 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/environments-about.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/environments-about.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/environments-about.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/environments-about.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/environments-about.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/environments-about.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/environments-about.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/environments-about.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/environments-about.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/environments-about.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/environments-about.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/environments-about.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/environments-about.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/environments-about.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/environments-about.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/environments-about.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/environments-about.md.txt)

An *environment* provides an isolated context or "sandbox" for running API proxies.
In a single organization, you can create multiple environments. For more information,
see [About environments and environment groups](https://docs.cloud.google.com/apigee/docs/api-platform/fundamentals/environments-overview.md.txt).


The following code shows an example overrides configuration where multiple environments are
defined. Note that environments
**prod** and **test** have different host aliases:

```
namespace: my-namespace
org: my-organization
...
envs:
  - name: test
    serviceAccountPaths:
      synchronizer: "your_keypath/synchronizer-manager-service-account.json
      udca: "your_keypath/analytic-agent-service-account.json

  - name: prod
    serviceAccountPaths:
      synchronizer: "your_keypath/synchronizer-manager-service-account.json
      udca: "your_keypath/analytic-agent-service-account.json
...
```
- Add a `virtualhosts` property that maps its `routingRules` to the environment(s).

  ```
  virtualhosts:
    - name: default
      hostAliases: ["api.example.com"]
      sslCertPath: ./certs/fullchain.pem
      sslKeyPath: ./certs/privkey.pem
      routingRules:
        - env: test
  ```

  ```
  virtualhosts:
    - name: external
      hostAliases: ["apiprod.example.com"]
      sslCertPath: ./certs/fullchain.pem
      sslKeyPath: ./certs/privkey.pem
      routingRules:
        - env: prod
  ```


  Suppose a proxy with the base path `/foo1` is deployed to environment
  **test**. You could call the proxy like this:

  ```
  curl -k https://api.example.com/foo1
  ```


  When this call hits the ingress, the ingress knows to send it to the message processor
  associated with the `test` environment, which handles the request.


  Similarly, if `foo1` is also deployed to the `prod` environment,
  you could make a proxy
  request like this, to the host alias `apiprod.mydomain.net`:

  ```
  curl -k https://apiprod.example.com/foo1
  ```


  And the call is routed by the ingress to the MP associated with that host.

  > [!NOTE]
  > **NOTE** On a request to an API proxy, the ingress compares the `Host` header of the incoming request to the list of host aliases to determine which virtual host handles the request. `curl` commands, browsers, and many other utilities automatically set the `Host` header with the domain of the request. If for any reason your app is not setting the `Host` header automatically, you must set it manually.


  **Antipattern**: Deploy all of your proxies to one hybrid environment.


  **Best practice** : Create multiple environments and deploy a limited number of proxies
  to each one. You can create routing rules that specify which environments
  to route specific API proxy basepaths to. For details, see [Virtual host configuration](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/base-path-routing.md.txt).

  ## Limit the number of proxy deployments


  For hybrid, the fact that many environments can share the same virtual host means
  that you must think carefully about how you manage your proxy deployments to any given
  environment. In hybrid, the best practice is to create multiple environments and deploy
  a limited number of proxies to each one.


  **How many proxies should you deploy to an environment?** There is not a set answer
  to this question; however, the following table provides general guidance on why it's a
  good idea to limit the number of proxies deployed to each environment and what you
  need to think about when managing proxy deployments:

  > [!NOTE]
  > **NOTE:** When deciding how many proxies to deploy to an environment, be sure to consider the product configuration limits described in [Limits](https://docs.cloud.google.com/apigee/docs/api-platform/reference/limits.md.txt#hybrid).

  | Issue to consider | Description |
  |---|---|
  | Message processor boot-up time | There is a direct correlation between the amount of time a message processor (MP) takes to boot up and the number of proxies deployed to that MP. In an auto-scaling Kubernetes environment, an increase in boot time might be a problem. The more proxies that are deployed to the MP, the longer it will take for that MP to come up if it needs to be scaled or recreated. |
  | Scaling performance | If you have several proxies deployed to an environment, and one of the proxies gets a lot of traffic so that it frequently auto-scales, all of the proxies in that environment will scale with it. The performance effect of scaling multiple proxies with a single high-traffic proxy might be a problem. |
  | Noisy neighbor | If you have several proxies deployed to the same environment, and one proxy crashes, then all of the proxies in the environment will be taken down while the MPs restart. By limiting the number of proxies deployed to an environment, you minimize the impact of a single proxy crashing. |

  ## Enviroment configuration reference


  For a complete list of environment configuration elements, see `envs` in the
  [Configuration property reference](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/config-prop-ref.md.txt#envs).

  ## Working with environments


  For more information about configuration, see the following topics:
  - [Creating new environments](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/environment-create.md.txt)
  - [Deleting environments](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/environment-delete.md.txt)
  - [Base path routing](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/base-path-routing.md.txt)