To Configure a Load Balancer for Anypoint Platform Private Cloud Edition

This product was previously named Anypoint Platform On-Premises Edition. Beginning with the 1.5.1 release, it is named Anypoint Platform Private Cloud Edition.

Anypoint Platform Private Cloud Edition should be run in production on more than one server, you must provide your own load balancer to enable this. A load balancer is necessary to distribute traffic between these, and to restrict open ports to just the necessary ones. You can use any standard tool for creating this load balancer, like NGINX.

Even if you plan to deploy the platform to a single server, a load balancer is strongly recommended.

You can configure this load balancer with any strategy you want, but a round robin strategy is most often the ideal.

This load balancer should be reachable through an IP address that is accessible by all machines in your network.

Your load balancer must route the following TCP ports:

Load Balancer Port Instance Port Internal Usage



HTTP redirects to HTTPs.



HTTPS port



WebSocket Port for Runtimes to connect



Ops Center Access Port



Monitoring Tooling Access Port

In every case, your load balancer must listen on the Load Balancer Port and redirect incoming requests to the Instance Port. Your installation of Anypoint Platform includes an internal NGINX server that listens on each of the Instance Ports and then performs the action listed in the Internal Usage column of the above table.

Additionally, your load balancer should poll the address HTTPS:10250/healthz to run a health check on your platform servers and confirm that they are accessible.

To configure SSL credentials, you don’t need to set them up in your load balancer. You can configure them via the Anypoint Runtime Manager.

To Configure a Load Balancer

:keywords:anypoint platform, on premises

You must manually create this load balancer as part of the installation procedure. You can create this load balancer with a tool other than NGINX.

  1. Enable stream block in your /etc/nginx/nginx.conf file, by referencing all the config from /etc/nginx/stream.d/*. You can achieve that by adding the following:

stream {
   include /etc/nginx/stream.d/*.conf;
  1. Delete the default.conf file from /etc/nginx/conf.d

  2. Create a folder named /etc/nginx/stream.d and in it create a file named onprem.conf

  3. Paste the following content in onprem.conf

server {
   listen 80;

server {
   listen 443;

server {
   listen 8889;

server {
   listen 9500;

server {
   listen 9501;


If you are installing the platform on an Amazon Web Services (AWS), you need to enable the default ports on SELinux before starting the NGINX. Run the following commands one by one:

`semanage port -a -t http_port_t  -p tcp 8889`
`semanage port -a -t http_port_t  -p tcp 9500`
`semanage port -a -t http_port_t  -p tcp 9501`
  1. Start NGINX service nginx restart

    If you are running the platform on an AWS, run the following command:

    `/usr/sbin/setsebool httpd_can_network_connect true`