> [!CAUTION]
> You are currently viewing version 1.15 of the Apigee hybrid documentation. 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.15 </button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/apigee-connect.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/apigee-connect.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/apigee-connect.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/apigee-connect.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/apigee-connect.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/apigee-connect.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/apigee-connect.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/apigee-connect.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/apigee-connect.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/apigee-connect.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/apigee-connect.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/apigee-connect.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/apigee-connect.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/apigee-connect.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/apigee-connect.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/apigee-connect.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/apigee-connect.html)

This section describes using Apigee Connect for communication between the hybrid management
plane and the MART service in the runtime plane.

## Introduction

Apigee Connect allows the Apigee hybrid management plane to connect securely to the MART service in
the runtime plane without requiring you to expose the MART endpoint on the internet. If you use
Apigee Connect, you do not need to configure the MART ingress gateway with a host alias and an
authorized DNS certificate.

![Primary services that execute on the hybrid runtime plane showing Apigee Connect](https://docs.cloud.google.com/static/apigee/docs/hybrid/v1.15/images/arch-runtime-apigee-connect.png "Runtime plane services")

## Configuring Apigee connect


Configure Apigee connect in your overrides with the [`connectAgent`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/config-prop-ref.md.txt#connectagent) configuration property.

### Service account


Apigee connect uses the [`apigee-mart`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/mart-service-account.md.txt) service account. This service account requires the Apigee Connect Agent `roles/apigeeconnect.Agent` role. See [Service accounts and roles used by hybrid components](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/sa-about.md.txt#recommended-sas).


Use the [`connectAgent.serviceAccountPath`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/config-prop-ref.md.txt#connectagent-serviceaccountpath) or [`connectAgent.serviceAccountRef`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/config-prop-ref.md.txt#connectagent-serviceaccountref) configuration properties to specify the `apigee-mart` service account key. Alternatively you can [store the service account key in Hashicorp Vault](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/storing-sa-keys-in-vault.md.txt).

### API


Apigee Connect requires the **Apigee Connect API** in the [Google Cloud API Library](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/cloud.google.com/endpoints/docs/openapi/enable-api). For instructions on enabling APIs in the Google Cloud console, see [Step 3: Enable APIs](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/precog-enableapi.md.txt).

### Applying Apigee connect configuration


Apply changes to the Apigee connect configuration with the `apigee-org` chart with the following command:

```
helm upgrade ORG_NAME apigee-org/ \
  --namespace apigee \
  --atomic \
  -f OVERRIDES_FILE.yaml
```

> [!NOTE]
> **Note:** If you see an error saying `Error: UPGRADE FAILED: "*ORG_NAME*" has no deployed releases`, replace `upgrade` with `install` and try the command again.

### Image


Apigee connect uses the `gcr.io/apigee-release/hybrid/apigee-connect-agent:1.15.10` image. If you want to use a private image repository, see [Use a private image repository with Apigee hybrid](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/container-images.md.txt).

## Checking Apigee connect logs


Check the Apigee Connect Agent log.

```
kubectl logs -n namespace apigee-connect-agent-pod-name
```

The Apigee Connect Agent reports the following log categories:  

| Audit logs category | Operations |
|---|---|
| DATA_READ | `ConnectionService.ListConnections` |
| DATA_WRITE | `Tether.Egress` |

For help on viewing audit logs in Apigee hybrid see [Audit logging information](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/audit-logging-info).

You can set the level of logging with the [`connectAgent.logLevel`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/config-prop-ref.md.txt#connectagent-loglevel) configuration property.