Step 3: Configuring Port Settings

Previous Step

Sisense uses certain ports to communicate with machines on the Internet and within your Sisense namespace. Below is a description of the ports that you may need to allow in your deployment.

Note: In cluster deployments, open all traffic between the nodes (TCP and UDP).

Outbound Rules for Sisense

Ports Description

80, 443

Allow outbound TCP connections from the workers to these ports to allow worker node updates and reloads.

2049

Allow outbound TCP and UDP to this port to allow mounting file storage as volumes.

This is only relevant when using NFS and only for the NFS server.

3260

Allow outbound TCP and UDP to this port for communication to block storage.

10250

Allow inbound TCP and UDP connections to this port for the Kubernetes dashboard and commands such as kubectl logs and kubectl exec.

For EKS, AES and GKE need to be open towards the K8S control.

Inbound Rules for Sisense

The following ports should be opened to your network so you will be able to access the Sisense application, SSH and Kubernetes dashboard:

Ports Description

TCP 443/30845

HTTPS/HTTP WEB (SSL/non-SSL mode). These ports should be open to allow your users to access Sisense.

TCP 22

SSH. This port should be opened when your Administrator needs to deploy or upgrade Sisense.

TCP 6443

This port should be opened when your Administrator needs to access the Kubernetes dashboard.

Cluster Mode

When deploying multiple nodes, the following ports should be opened between each node:

Ports Description

TCP 2379 - 2380

etcd

TCP 10248 - 10259

Kubernetes

TCP 9100

Node exporter

Cluster Network Plugin

Sisense support two cluster network plugins, Calico and Weave. The default network plugin used by Sisense is Calico.

Calico and Weave secure the communication between your nodes. The following ports should be opened:

Calico

Ports Description

TCP 9099

Calico

TCP 179

Calico - bird

Weave

Ports Description

TCP 6783

Weave’s control and data

UDP 6783/6784

Weave’s control and data

UDP 4789

VXLAN

TCP 111

rpcbind

TCP 179

bird

Cluster Shared File System Implementation

Sisense supports GlusterFS or Amazon EFS for shared storage. Depending on which you use, the following ports should be opened: 

GlusterFS

Ports Description

TCP 24007

Gluster Daemon

TCP 111

rpcbind

TCP 49152-49251

GlusterFS

TCP and UDP 24007 - 24008

Gluster servers

FSx

Ports Description

TCP 988

NFS

NFS/Amazon EFS

Outbound EFS/NFS should fo rthe nodes and EFS itself

Ports Description

TCP 2049

NFS

When using Amazon EFS, make sure that Sisense instances VPC is opened to the EFS security group.

Amazon EFS should be exposed to your server

Load Balancer

If you are using an external load balancer, make sure that the load balancer supports WebSockets.

If you are using Amazon AWS with load balancing, ALB supports WebSockets, ELB does not.

Next Steps