You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs/api-platform/system-administration/options-configuring-tls). info

## Apigee Edge

The following figure shows where Apigee Edge for Private Cloud customers configure TLS:

![](https://docs.apigee.com/static/api-platform/images/EdgeSSLOPDK_v2.png)

The following table describes the locations where you configure TLS access for a Private Cloud
installation:

|   | **Source** | **Destination** | **TLS Access** |
|---|---|---|---|
| 1 | API developer | Edge management UI | Enable TLS on the Edge UI for either the New Edge experience or the Classic UI: - [Configuring TLS for the New Edge experience](https://docs.apigee.com/private-cloud/latest/configuring-tls-ue) - [Configuring TLS for the management UI (Classic UI)](https://docs.apigee.com/private-cloud/latest/configuring-ssl-management-ui) See the Edge *Operations Guide* for more, which is available from your private FTP account or on the [Apigee Support Portal](https://apigee.com/about/support/portal) under **Libraries** (Edge for Private Cloud version 4.16.01 and earlier) |
| 2 | API Developer | Edge management API | Enable TLS on the Edge management API. See the Edge *Operations Guide* for more, which is available from your private FTP account or on the [Apigee Support Portal](https://apigee.com/about/support/portal) under **Libraries** (Edge for Private Cloud version 4.16.01 and earlier) and online at [Configuring TLS/SSL for Edge On Premises](https://docs.apigee.com/private-cloud/latest/configuring-ssl-edge-premises) (version 4.16.05 and later). |
| 3 | API Client (app) | API | Enable TLS on API access through the use of virtual hosts on the Edge Router. See [Configuring TLS access to an API for the Private Cloud](https://docs.apigee.com/api-platform/system-administration/creating-virtual-host) for more. |
| 4 | Edge | Target endpoint | Enable TLS between Edge and a backend service provider. See [Configuring TLS from Edge to the backend (Cloud and Private Cloud)](https://docs.apigee.com/api-platform/system-administration/configuring-ssl-edge-backend-service) for more. |
| 5 | Router | Message Processor | Enable TLS for communication between a Router and Message Processor. See the Edge *Operations Guide* for more, which is available from your private FTP account or on the [Apigee Support Portal](https://apigee.com/about/support/portal) under **Libraries** (Edge for Private Cloud version 4.16.01 and earlier) and online at [Configuring TLS/SSL for Edge On Premises](https://docs.apigee.com/private-cloud/latest/configuring-ssl-edge-premises) (version 4.16.05 and later).. |

If your Edge for Private Cloud installation included a load balancer, then you might also have
to replace the configuration for #3 above to configure TLS between the app and load balancer, and
between the load balancer and the Edge Router:

|   | **Source** | **Destination** | **Description** |
|---|---|---|---|
| 6 | App | Load Balancer | Enable TLS on the load balancer. This process is determined by your load balancer. |
| 7 | Load Balancer | Router | If necessary, enable TLS on the Router for requests from the load balancer. Use the same process as you do for configuring TLS for a virtual host as described here: [Configuring TLS access to an API for the Private Cloud](https://docs.apigee.com/api-platform/system-administration/creating-virtual-host). If the load balancer and Router are in the same security domain, TLS configuration may not be necessary. However, that is dependent on your network configuration. |

**Learn more:**

- [About TLS/SSL](https://docs.apigee.com/api-platform/system-administration/about-ssl)
- [Using TLS with
  Edge](https://docs.apigee.com/api-platform/system-administration/using-ssl-edge)
- [About virtual hosts (Beta)](https://docs.apigee.com/api-platform/fundamentals/virtual-hosts)
- [Keystores and
  Truststores](https://docs.apigee.com/api-platform/system-administration/keystores-and-truststores)