When using a load balancer, you can configure TLS between the API client and the load balancerĪnd, if necessary, between the load balancer and the Router, as the following tableĪpps access your APIs by making requests to API proxies through a load balancer. However, you can configure two-way TLS on the Router. Note: Load balancers often cannot be configured to support two-way In a Private Cloud installation, the presence of a load balancer is dependent on your network configuration The following image shows a scenario where the API client accesses Edge through a loadīalancer, rather than accessing the Router directly: Private Cloud customers can use a load balancer before the Router to handle requests. The Cloud-based version of Edge is typically configured so that all request from the API clientĪre handled by the Router. The request, balances requests across available Message Processors, and dispatches the Message Processor accesses your backend service in response to a request to an APIĪ Router handles all Edge incoming API traffic, determines the API proxy that handles Target endpoint, which is often defined by an endpoint on your backend service. Products, create and manage apps and app developers, and to perform many other types ofĪpps access your APIs by making requests to API proxies through virtual hosts on theĪn API proxy functions as a mapping of a publicly available endpoint on Edge to a That means you can use these APIs to create, configure, and manage API proxies and API Of the tasks necessary to create, configure, and manage API proxies and API products.Īll Edge services can be configured through the Edge management API, a REST-based API. The Edge management UI is a browser-based tool that API developers use to perform most The following table describes these TLS connections: To configure TLS for connections 3 and 4 shown in the figure. However, for Cloud customers, Apigee handles most of the TLS configuration for you and only have Note: Most of the connections between the Edge components have beenĪpigee Edge for Private Cloud customers typically configure all connections to use TLS. The following images shows the places in an Edge installation where you can configure TLS: Support for TLS versions 1.0 and 1.1 for the Cloud The supported versions of TLS depend on whether you are using Edge in the Cloud or That means you not only have to obtain the TLSĬertificate and private key, but you also have to configure Edge to use TLS. Private Cloud deploymentįor an Apigee Edge for Private Cloud installation of the Developer Services portal, you areĬompletely responsible for configuring TLS. Information on Edge pricing plans, see Apigee pricing.įor the Cloud version of the Developer Services portal, you configure TLS on on the Pantheon Secure virtual host so that trial customers can get started developing and testing APIs. Instead, Apigee automatically provides a TLS certificate and private key to support HTTPS on a Note: Free and trial accounts cannot configure TLS for API proxies. To API proxies and your target endpoints. In a Cloud-based deployment of Edge you are only responsible for configuring TLS access The Edge TLS configuration procedure depends on how you deployed Edge: ApigeeĮdge Cloud or Apigee Edge for Private Cloud. In addition, EdgeĪdd-ons, such as the Developer Services portal, have entry points that can be configured to use View Apigee X documentation.Īpigee Edge has several entry points that you might want to secure with TLS. You're viewing Apigee Edge documentation.
0 Comments
Leave a Reply. |