Using TLS in Private Cloud Installation for a standalone and 5 host installation topology

[#1]

Based on : https://docs.apigee.com/private-cloud/v4.18.01/installation-topologies

Standalone Topology:-

For Test environment, we only have a single frontend server to host the Edge UI, Developer Portal, Router/Message Processor. Is it possible to achieve TLS (HTTPS connection) using the default port 443 itself for all these components? Or will it cause conflict as two or more components cannot listen to port 443 at the same time? How can we achieve this since we can only have port 443 exposed to outside world.

5 host installation topology:-

Do we require a load balancer for the Router/Message Processor cluster? In case of 5 host installation, where can we install Developer Portal? Do we need a 6th server for that?

[anilsr · Accepted solution]

@Jaideep Menon ,

Regarding, Test Environment,

• You need to expose different services on different ports. You can enable TLS (HTTPS) on other ports too apart from 443, For example how to enable TLS for Management Server on port 8443 here. https://docs.apigee.com/private-cloud/v4.17.01/configuring-tls-management-api . You can find related information in Apigee Docs.

5 host installation topology:-

• Yes, Developer Portal will be installed on 6th server. Yes, You need an ELB that frontend Routers.

Hope it helps.

[#3]

@Anil Sagar, We are trying to accomplish it without much change to the internal firewall settings which only allows incoming to port 443. Also, we are trying to avoid having the port number in the URLs. Is it possible with the help of Nginx as reverse proxy?