Skip to main content
Version: 10.2.4

Ports

Open the following ports on the servers. The same open ports must be specified in the ports.yml file later during the installation.

The following table lists the default ports for each application component.

Access types:

  • External for end-users
  • Internal for internal application communication

Keep all IA Cloud environment servers in the same single subnet with restricted EXTERNAL access to this subnet (close all ports from outside the subnet) and NON-restricted internal access between servers (keep all ports open between all servers within the subnet). Such an approach allows communication between product components located on different hosts between each other. To ensure network security, consider using firewalls in your network to block requests outside the subnet where your environment is located.

To ensure that end-users can interact with the Product, on the Master server, open specific ports externally. By default, the ports are 80 and 443, but you can change them if needed. For the high-availability mode, 80 and 443 must be open only on a Load Balancer.

This is the easiest and secure way to ensure that your data and application are protected from the network perspective.

The table below describes which ports on which servers are used for communication between components.

Suppose you decide to configure firewall rules granularly per each network interface (for each server) using IPTables or FirewallD on each server. In that case, there is a high risk of human factor mistakes caused by multiple rules for each host. It is easy to forget to open some specific port FROM some specific server TO some particular server. In this case, installation may fail in unpredictable places which are difficult for troubleshooting, or the Product will not work correctly. That's why the recommended approach of securing your network is to use a dedicated secured subnet with open internal communication and closed external requests.

Default ports​

See tab Basic setup or HA setup and update from earlier versions, depending on your installation method. On the specified servers (column Destination server), open the ports (column Destination Port) to the required servers (column Source server). If the Source server cell contains "All servers", you must open the corresponding port both ways: to and from ALL existing servers, including the destination server.

In case of the basic installation, open the following ports:

Source serverDestination serverDestination portService nameAccess typeDescription
All serversMaster80, 443/tcpHAProxy (proxy for Control Tower, Workspace, bot-manager, AutoQC, Nexus, Minio, Tinymce, Kibana)externalThe main product port for accessing from browser
All serversMaster2181/tcpZooKeeperinternalListens to 0.0.0.0 (ZK). ZooKeeper port.
All serversMaster2281/tcpZooKeeperinternalListens to 0.0.0.0 (ZK). ZooKeeper secure port.
All serversMaster4567-4571/tcp, 15072-15073/tcplogstashinternalListens to 0.0.0.0 (HTTPS). Logstash port.
All serversMaster5672/tcpRabbitMQ queueinternalListens to 0.0.0.0 (TLS ecrtypted AMQP). RabbitMQ message Queue port.
All serversMaster8202/tcpHAProxy (proxy for Vault)internalListens to 0.0.0.0 (TCP). HAPROXY and Load Balancer port for Vault.
All serversBI80, 443/tcpApache (proxy for Tableau Web Interface)externalThe main product port for accessing from the browser
All serversMSSQL1433MS SQLinternalMS SQL Server port
MasterMaster7373/tcpKESinternalOnly for 10.2.4.2. Listens to 0.0.0.0 (HTTPS). KES port.
MasterMaster7374/tcpHAProxy (proxy for KES)internalOnly for 10.2.4.2. Listens to 0.0.0.0 (TCP). HAPROXY and Load Balancer port for KES.
MasterAgent22/tcpSSHinternalSSH port listening on all Linux servers. Used by the installer in a single-point installation.
MasterAgent5051/tcpmesos-slaveinternalListens to 0.0.0.0 (HTTPS). Mesos Agent port.
MasterAgent40000-44000/tcpmesos-slaveinternalListens on 0.0.0.0 (HTTPS). Port range on Mesos Agent(s) used for communication with Mesos Master.
MasterBI5986/tcpWinRMinternalWindows Remote Management (WinRM) HTTPS port listening to Windows servers. Used by the installer in a single-point installation.
MasterRPA5986/tcpWinRMinternalWindows Remote Management (WinRM) HTTPS port listening to Windows servers. Used by the installer in a single-point installation.
MasterRPA8443/tcpnginx (proxy for RPA hub)internalListens to 0.0.0.0. Nginx HTTPS port. Used to proxy requests from Haproxy (from lb_port_ssl) to destination product components.
AgentMaster111/tcp+udpNFSinternalDon't change it. NFS portmap TCP and UDP port. Used by internal NFS server only in non-HA mode, and only when nfs_enabled: True
AgentMaster2049/tcp+udpNFSinternalDon't change it. NFS daemon TCP and UDP port. Used by internal NFS server only in non-HA mode, and only when nfs_enabled: True
AgentMaster5050/tcpmesos-masterinternalListens to 0.0.0.0 (HTTPS). Mesos master port.
AgentMaster8480/tcpnginx (proxy for marathon)internalDon't change it. Listens to 0.0.0.0 (HTTPS). Marathon Port.
AgentMaster9073/tcpnginx (mTLS for AutoML gateway-service)internalListens to 0.0.0.0 (HTTPS). Nginx port. Proxies requests to ags_port.
AgentMaster9702/tcphazelcast server communication portinternalDon't change it. Listens to 0.0.0.0 (HTTPS). Hazelcast server port.
AgentMaster20048/tcp+udpNFSinternalDon't change it. NFS mountd TCP and UDP port. Used by internal NFS server only in non-HA mode, and only when nfs_enabled: True
AgentAgent5051/tcpmesos-slaveinternalListens to 0.0.0.0 (HTTPS). Mesos Agent port.
AgentAgent40000-44000/tcpmesos-slaveinternalListens on 0.0.0.0 (HTTPS). Port range on Mesos Agent(s) used for communication with Mesos Master.
RPAMaster9073/tcpnginx (mTLS for AutoML gateway-service)internalListens to 0.0.0.0 (HTTPS). Nginx port. Proxies requests to ags_port.
RPAMaster9702/tcphazelcast server communication portinternalDon't change it. Listens to 0.0.0.0 (HTTPS). Hazelcast server port.

Ports for Mesos and Marathon Web UI​

If you plan to access the Marathon web interface (for example, to monitor workers or view their configuration), open the following ports for external access. For security reasons, you can allow access only from particular IP addresses, for example, developer, or operator workstations, using this feature:

Source serverDestination serverDestination portService nameAccess type
Operators workstationsMaster server(s)8480mesos-masterexternal

Ports for external NFS server​

If you plan to use an external NFS server, open the following ports in addition to the ones mentioned earlier:

Source serverDestination serverDestination portService nameAccess type
All serversNFS111/tcp+udpNFSinternal
All serversNFS2049/tcp+udpNFSinternal
info

In case you have MOUNTD_PORT, STATD_PORT, LOCKD_TCPPORT, and LOCKD_UDPPORT statically defined on your NFS server, make sure that traffic is allowed from all IA Cloud servers towards these ports on the NFS server. Otherwise, ensure that traffic is permitted from all IAC servers towards the port range 1024 to 65535 on the NFS server.

WorkFusion URLs​

Master (in non-HA mode) or LoadBalancer (in HA mode):

  • https://workfusion_lb_hostname: Control Tower
  • https://workspace_lb_hostname/workspace: Workspace
  • https://kibana_lb_hostname/kibana/: Kibana
  • https://minio_lb_hostname/minio: MinIO (S3 emulator)
  • https://nexus_lb_hostname/nexus: Nexus
  • https://rabbitmq_lb_hostname: RabbitMQ API Web UI
  • https://mesos_lb_hostname: Mesos
  • https://marathon_lb_hostname: Marathon
  • https://ocr_lb_hostname: OCR Rest API
  • https://bi_lb_hostname: Tableau web interface
  • https://keycloak_lb_hostname: Keycloak web interface