# Installing Sisense on Linux

> How to install Sisense.

*Source: https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-linux.htm*

---

Last updated: June 10, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Enterprise | On-Prem |

Note:

Sisense may provide configuration recommendations in an attempt to assist with integrating third-party solutions (e.g., monitoring, storage type solutions, etc.) to work better with Sisense; however, Sisense is not responsible for installing or supporting any such third-party solutions.

Ensure that you thoroughly review [Minimum Requirements for Sisense in Linux Environments](https://docs.sisense.com/main/SisenseLinux/linux-minimum-requirements.md) and [Checking the Prerequisites](https://docs.sisense.com/main/SisenseLinux/checking-the-prerequisites.md) before installation.

Pre-Installation:

1. Backup the Sisense servers prior to installation, for rollback purposes.
2. If you want to use a user other than the default user in Linux, create a `sudo` enabled user account for each server that Sisense will be deployed on.

   Check which privileges each user has to run `sudo`:

   `sudo -l -U <installation user>`

   The response to this command must include the following:

   `(ALL : ALL) NOPASSWD: ALL`

   It is recommended that the user has a UID/GID of 1000. Run the following command to check user's UID/GID:

   `id -u <installation user>`

   If you need to use a user with a UID/GID other than 1000, see [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md).
3. Log in to an SSH session with the installation user you created.
4. Navigate to the directory that you will install from.

   `cd sisense-installation-directory`
5. Deployment

   Sisense supports four types of deployment:

   - Single-node
   - Cluster (multi-node)
   - OpenShift
   - Cloud-based Kubernetes

   Contact your Sisense Customer Success Manager to receive the link to the latest Linux archive file. The archive includes five configuration files, one for each of the deployment types and a generic config.yaml file that contains all of the parameters for each deployment.

   Follow the instructions for your type of deployment in the relevant drop-down option below:

   [Single Node Deployments on RKE](#)

   **Before you set up Sisense on your single Linux machine, you must mount /opt on a dedicated disk. For instructions on how to mount /opt, see** [Mounting on a Dedicated Disk for Sisense Single Nodes](https://docs.sisense.com/main/SisenseLinux/mounting-on-a-dedicated-disk-for-sisense-single-nodes.md).

   Notes:

   - Before you install Sisense, all Linux non-root users must have sudo permissions to initialize Sisense. From Sisense Linux V8.2.1, Sisense services only run as part of the Sisense user and do not use Root user permissions. If you must install Sisense as a Root user, see [Sisense Service Permissions](https://docs.sisense.com/main/SisenseLinux/sisense-service-permissions.md).
   - If you are deploying Sisense on Red Hat Enterprise Linux 8.4, execute the following commands prior to running the Sisense installation:   
     `sudo systemctl disable nm-cloud-setup.service nm-cloud-setup.timer`  
     `sudo reboot`  
     You must reboot or the changes will not be applied. Thereafter, install Sisense as usual.

   Make sure you have enough disk space on the disk you mount. The disk must include 50GB + 2\*(size of the ElasticCube data), with no less than 50GB.

   **To initialize Sisense in a Linux environment:**

   1. Using the sudo user you created, in the Linux CLI, enter the following command to download the Sisense tar.gz file.

      wget [sisense-linux-deployment-link]
   2. Extract the tar.gz file into the {`sisense-version`} folder:

      tar zxf [sisense-linux-deployment-package-name]
   3. Navigate to the {`sisense-version`} directory where you extracted the tar.gz file.

      cd sisense-[sisense-version]
   4. Edit the single\_config.yaml file.

      vim single\_config.yaml
   5. In the single\_config.yaml file, you must enter values for the following parameters:

      | **Parameters** | **Value** |
      | --- | --- |
      | k8s\_nodes - { node: [name], internal\_ip: 0.0.0.0, external\_ip: 0.0.0.0 } | K8S node/nodes are the set of machines that are used to run Sisense.  This parameter sets:  - *node* ***-*** The DNS name of your node. Changing the node name changes the hostname when the installer runs. - *internal\_ip* - The internal IP address defines the location within your Kubernetes cluster. - *external\_ip -* The external IP address sets how your cluster can be accessed from outside, or the DNS name of the node. It can have the same value as the internal IP if this is the only IP used to access the node. **Note:**  Node names may not include uppercase letters. Node names can only include lowercase letters, digits and hyphens. Hyphens cannot be the last character in the node name.  The installation machine is only used during installation to run the installation scripts. The installation machine can be one of the K8S nodes, or it can also be a different machine (remote installation). |
      | deployment\_size: "small" | To increase the pod resource limits allocated for the application, set deployment\_size to large. |
      | cluster\_visibility: true | For security restrictions that revoke cluster role permissions, set cluster\_visibility to false to disable the following Sisense workflows:  - Watching Sisense Nodes that exist or are added to the cluster (e.g. for the data-groups feature). In this case, use the manual labeling method. - Updating the logging system with the customer-registered owner ID. |
      | offline\_installer: false | Set offline\_installer to **true** when you are using an offline installer. |
      | #docker\_registry: "" | (Optional) Only required if you are using an offline installer (offline\_installer = true).  Enter your server's address. |
      | **Note:**  If you are using a private docker registry, you must either:  - Use a docker username & password (the following two parameters below), and the installer will create the secret for you  OR - You can manually create your own pull secret and use the `pull_secrets_name` parameter (the third parameter below) | |
      | #docker\_username: "" | (Optional) Only required if you are using a private registry and the installer will create the secret.  Enter your docker's username. |
      | #docker\_password: "" | (Optional) Only required if you are using a private registry and the installer will create the secret.  Enter your docker's password. |
      | #pull\_secrets\_name: "" | (Optional) Only required if you have entered a value for the docker\_registry parameter and you will manually create the secret.  Enter the Docker secret name if your registry is private. |
      | remote installation: false | If you are running your installation from a bastion machine (part of the K8S nodes), or remotely, set this to **true**. |
      | update: false | If you are upgrading Sisense, set this to **true**, otherwise, keep this default value.  If you enter **true**, Sisense skips the Kubernetes installation. If your Kuberenetes cluster is already configured and running, keep **yes** to skip cluster installation.  Staging and dev environments can run on the same cluster as a separate namespace. To install on a separate namespace, see [Setting Up Multiple Instances of Sisense](https://docs.sisense.com/main/SisenseLinux/setting-up-multiple-instances-of-sisense.md). |
      | Notify\_On\_Upgrade: true | If set to true, the Sisense application will not be accessible during upgrades. Instead, a system maintenance notification will appear. |
      | update\_k8s\_version: false | To update the Kubernetes version, set this to **true**. |
      | cni\_plugin: | Enables the user to set their preferred CNI (Container Network Interface) while deploying a new Kubernetes.  Valid values: calico (default), flannel  **Note:**  When update\_k8s\_version is set to true, you must set this to your currently existing CNI value. (You can find your CNI value with the command:`kubectl get pod -n kube-system | grep 'calico\|flannel'`. |
      | .application\_dns\_name: "" | Enter the DNS name.  - If no DNS name is entered, the default value is the external IP of the first node in the cluster. - If the is\_ssl parameter is set to true, enter the Common Name for this parameter. - If an external load balancer is used for the Common Name, add the http:// or https:// prefix to the   entry. **Note:**   - You can only define this parameter when installing or upgrading Sisense. After defining this value,   you can view this value under General Settings in the Sisense Admin page. - The Web Server Alias must only contain the domain name, for example, https://secure.mydomain.com. It   must not contain a deep link, for example,   https://secure.mydomain.com/ReportingAdvanced/AdvancedDashboarding.aspx?myurl=. |
      | linux\_user: "sisense" | Enter the name of the Linux user. This user must not be the "root" user, but should have sudo privileges, and all the other privileges of a root user. |
      | ssh\_key: "" | Enter the SSH key if you have a secure connection to your server. This is the SSH key of the Linux user set in the **linux\_user** parameter. The SSH key must be in .pem format. |
      | Enter the name of the Kubernetes namespace. By default, the namespace is Sisense. | Enter the name of the Kubernetes namespace. By default, the namespace is Sisense.  **Note:**  Kubernetes ports should be released (Non-listening mode). |
      | gateway\_port: 30845 | Enter the port of the API gateway for your deployment. Do not set this port to 443 if setting up SSL.  If you are not implementing SSL, this is the port used to connect to Sisense. |
      | timezone: "UTC" | Enter the system time zone based on the [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (i.e., UTC, US/Central, Asia Tokoyo, Etc/GMC+6). |
      | is\_ssl: false | Set the value to **true** for secure connections to Sisense.  Set the value to **false** if you have not implemented SSL.  If set to true, see [Setting Up SSL for Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/setting-up-ssl-for-sisense-linux.md). |
      | ssl\_key\_path: "" | If you connect to your server securely, enter the SSL keypath.  When the SSL is defined, the Sisense API Gateway Port will be 443 and not the value defined in the Gateway\_port parameter. |
      | ssl\_cer\_path: "" | If you connect to your server securely, enter the SSL certificate path to the .cer file. |
      | #http\_proxy: | (Optional) If you use a web proxy, enter the unsecured proxy value.  **Note:**  If your Linux system uses a proxy server for external traffic and no proxy for local traffic, you must complete the system configuration and Sisense configuration steps in [Configuring for Linux Installation on a Proxy, No Proxy System](https://docs.sisense.com/main/SisenseLinux/configuring-for-linux-installation-on-a-proxy-no-proxy-system.md) before initializing Sisense on your system. |
      | #https\_proxy: | (Optional) If you use a web proxy, enter the secured proxy value. |
      | #no\_proxy: | (Optional) If you use a web proxy, enter the address(es) to exclude from your proxy. Use commas to separate multiple IP addresses.. |
      | internal\_monitoring: true | When set to **true**, Sisense installs a Prometheus/Grafana/Flunetd dashboard. To disable a Prometheus-supported Grafana dashboard from monitoring your deployment, set this to **false.** See [Monitoring Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/monitoring-sisense-on-linux.md) and [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | uninstall\_cluster: false | To remove the Kubernetes infrastructure and Sisense services, set this to **true**. |
      | uninstall\_sisense: false | To uninstall Sisense services, but leave your Kubernetes infrastructure unchanged (if it is needed in the future), set this to **true**. |
      | remove\_user\_data: false | To delete all user data, set this to **true**. This deletes your ElastiCube models, application database, message broker, and add-ons. |
      | signature\_validation: false | Enter **true** to enable [Image Signature Validation](https://docs.sisense.com/main/SisenseLinux/image-signature-validation.md). |
      | delete\_local\_images: false | For offline customers. Enter **true** for when uploading images to your private registry (command `bash ./installer/offline/offline_installer.sh upload ${CONFIG_FILE} <USERNAME>`), after each successful upload, it will delete the image from your local registry on your server and will also remove the `.tar` of that image from the installation dir in your local file system, thereby saving a lot of space on your server. |
   6. Run the configuration script.

      ./sisense.sh single\_config.yaml

      Your configuration settings are displayed with a message to confirm that you want to deploy Sisense with these settings.
   7. Enter **Yes** to confirm that you want to deploy Sisense, or enter **No** to abort the deployment. If there are any issues when the deployment script finishes, view the installation logs as follows:

      [installation-dir]/sisense-ansible.log

   When the installation finishes a list of endpoints are displayed for accessing Sisense and managing your deployment. Additionally, you can run the following command to return the URL to access Sisense:

   kubectl cluster-info

   This command returns the URL of your Sisense application. You can enter this address into your browser to access Sisense. To verify that all your services are running as expected, you can enter the Sisense URL with the port and /app/test added to the end of the address in your browser. This displays the status of each of your services. For example:

   0.0.0.0:PORT/app/test

   To connect to Sisense, enter the URL address into your browser:

   - For non-secure connections:`http://{IP}:30845/`
   - For secure connections:`https://{IP}/`

   To connect to your Kubernetes dashboard, enter the following URL in your browser:

   https://{IP}:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy

   [Cluster (Multi-Node) Deployments on RKE](#)

   The instructions below describe how to deploy Sisense in a cluster deployment.

   **Note:**

   - If your cluster deployment is on EC2 with FSX for Lustre, see [Deploying Sisense on EC2 with Amazon FSx for Lustre](https://docs.sisense.com/main/SisenseLinux/deploying-sisense-on-ec2-with-amazon-fsx-for-lustre.md).
   - If you are deploying Sisense on Red Hat Enterprise Linux 8.4, execute the following commands for each node prior to running the Sisense installation:   
     sudo systemctl disable nm-cloud-setup.service nm-cloud-setup.timer  
     sudo reboot  
     You must reboot or the changes will not be applied. Thereafter, install Sisense as usual.

   **Important:**

   Before you install Sisense, all Linux non-root users must have sudo permissions to initialize Sisense. From Sisense Linux V8.2.1, Sisense services only run as part of the Sisense user and do not use Root user permissions. If you must install Sisense as a Root user, see [Sisense Service Permissions](https://docs.sisense.com/main/SisenseLinux/sisense-service-permissions.md).

   **To install Sisense in a cluster deployment:**

   1. In the Linux CLI, execute the following command to download the Sisense tar.gz file.

      wget [sisense-linux-deployment-link]
   2. Extract the tar.gz file:

      tar zxf [sisense-linux-deployment-package-name]
   3. Navigate to the directory where you extracted the tar.gz file.

      cd sisense-[sisense-version]
   4. Edit the cluster\_config.yaml file.

      vim cluster\_config.yaml

      After running this command, the parameters of the cluster\_config.yaml file are displayed.
   5. In the cluster\_config.yaml file, populate values for the following parameters:

      **Note:**

      If you have multiple deployments, assign a unique namespace for each deployment. For example, there might be development and production environments. Additionally, for multiple deployments, each environment must have a unique gateway\_por

      | **Parameters** | **Value** |
      | --- | --- |
      | k8s\_nodes - { node: node1, internal\_ip: 0.0.0.0, external\_ip: 0.0.0.0, disk\_volume\_device: /dev/sdb, roles: "application, query" } - { node: node2, internal\_ip: 0.0.0.0, external\_ip: 0.0.0.0, disk\_volume\_device: | The K8S nodes are the set of machines that will be used to run Sisense.  If you are implementing a multi-node cluster deployment, define the following for *each* node:  **node**: The DNS name of your node.  **Note:**  Node names may not include uppercase letters. Node names can only include lowercase letters, digits and hyphens. Hyphens cannot be the last character in the node name.  **internal\_ip**: Enter the address of the location of your node within your Kubernetes cluster.  **external IP**: This address determines how your cluster can be accessed from outside, or the DNS name of the node. It can also be the same value as the internal IP if this is the only IP used to access the node.  **roles**: Sets the role of the node. Valid values: *application*, *query*, and *build*.  The installation machine is only used during installation, to run the installation scripts. The Installation machine can be one of the Kubernetes nodes, but it can also be a different machine (for remote installation). |
      | deployment\_size: "small" | To increase the pod resource limits allocated for the application, set deployment\_size to **large**. |
      | cluster\_visibility: true | For security restrictions that revoke cluster role permissions, set cluster\_visibility to false to disable the following Sisense workflows.  - Watching Sisense Nodes that exist or are added to the cluster (e.g. for the data-groups   feature). In this case, use the manual labeling method. - Updating the logging system with the customer-registered owner ID. |
      | offline\_installer: false | Set to **true** when you are using an offline installer. |
      | #docker\_registry: "" | (Optional) Only required if you are using an offline installer (offline\_installer = true). Enter your server's address. |
      | **Note:**  If you are using a private docker registry, you must either:  - Use a docker username & password (the following two parameters below), and the installer will create the secret for you  OR - You can manually create your own pull secret and use the `pull_secrets_name` parameter (the third parameter below) | |
      | #docker\_username: "" | (Optional) Only required if you are using a private registry and the installer will create the secret.  Enter your docker's username. |
      | #docker\_password: "" | (Optional) Only required if you are using a private registry and the installer will create the secret.  Enter your docker's password. |
      | #pull\_secrets\_name: "" | (Optional) Only required if you have entered a value for the docker\_registry parameter and you will manually create the secret.  Enter the Docker secret name if your registry is private. |
      | update: false | If you are upgrading Sisense, set this to **true**. Otherwise, use **false** as the default value.  If you set this to true, Sisense skips the Kubernetes installation.  If your Kuberenetes cluster is already configured and running, keep true to skip cluster installation. |
      | Notify\_On\_Upgrade: true | If set to true, the Sisense application will not be accessible during upgrades. Instead, a system maintenance notification will appear. |
      | remote\_installation: false | If you are running your installation from a bastion machine (part of the Kubernetes nodes), or remotely, set this to **true**. |
      | application\_dns\_name: "" | Enter the DNS name.  - If no DNS name is entered, the default value is the external IP of the first node in the   cluster. - If the *is\_ssl* parameter is set to true, enter the Common Name for this parameter. - If an external load balancer is used for the Common Name, add the http:// or https:// prefix to   the entry. **Note:**  - You can only define this parameter when installing or upgrading Sisense. After defining this   value, you can view this value under **General Settings** in the Sisense   **Admin** page. - The Web Server Alias must only contain the domain name, for example,   https://secure.mydomain.com. It must not contain a deep link, for example,   https://secure.mydomain.com/ReportingAdvanced/AdvancedDashboarding.aspx?myurl=. |
      | linux\_user: "sisense" | Enter the name of the Linux user.  This user must not be the "root" user, but must have sudo privileges, and all the other privileges of a root user. See [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | run\_as\_user: 1000 | The user ID that will perform the installation. This will also be used in the SecurityContext.runAsUser setting for Sisense services (pods). See [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | run\_as\_group: 1000 | The user group ID that will perform the installation.  This will also be used in the SecurityContext.runAsGroup setting for Sisense services (pods). See [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | fs\_group: 1000 | The SecurityContext.fsGroup setting for the Kubernetes pods. Kubernetes recursively changes ownership and permissions for the contents of each volume to match the fsGroup specified in a pod's securityContext when that volume is mounted. See [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | ssh\_key: "" | Enter the SSH key if you have a secure connection to your server. This is the SSH key of the Linux user set in the linux\_user parameter. The SSH key must be in .pem format. |
      | high\_availability: true | **True** means that Sisense is scaled for service redundancy.  **False** means that Sisense will not scale its services. |
      | storage\_type: "" | Valid values:  **nfs**: For using an external NFS server as the shared storage. You must define the nfs\_server and nfs\_path parameters, and have root read/write permissions for the Sisense system installation user on the path from the cluster hosts. Note that Sisense requires NFS v4 implementation of NFS.  **fsx**: For using an Amazon FSX cluster. You must also enter values for fsx\_dns\_name and fsx\_mount\_name. |
      | fsx\_dns\_name: "" | If your system uses AWS FSx services, enter the associated DNS alias name. |
      | fsx\_mount\_name: "" | If your system uses AWS FSx services, enter the mount name for the file system. |
      | nfs\_server: "" | Enter your NFS server's address (IP or DNS). |
      | nfs\_path: "" | Enter your NFS server's location.  The mounting point for each logical disk (Sisense app, MongoDB, and Zookeeper) is created under this path. |
      | mongodb\_disk\_size: 20 | Enter the amount of disk space allocated for the Sisense application database.  Multiply this value by the number of nodes used in your deployment.  It is recommended to leave the default of 20GB. If only metadata is stored in the MongoDB, there is no need to increase the size. |
      | zookeeper\_disk\_size: 2 | Enter the amount of disk space allocated for the ZooKeeper service.  If you have several deployments, this number is the sum of all the zookeeper disk sizes of all the deployments. It must be at least 2GB.  It is recommended to leave the default of 2GB. If only metadata is stored in Zookeeper, there is no need to increase the size. |
      | timezone: "UTC" | Enter the system time zone applicable to the time zone of the relative date-time filters. Format: [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (i.e., UTC, US/Central, Asia Tokyo, Etc/GMC+6). |
      | namespace\_name: sisense | Enter the name of the Kubernetes namespace. By default, the namespace is Sisense.  If you have multiple deployments, use a unique namespace for each deployment. For example, there might be development and production environments.  Additionally, for multiple deployments:  - Each environment must have a unique`gateway_port`value. - After the first deployment, the value of the update parameter must be set to   **true**. **Note:**  Kubernetes ports should be released (Non-listening mode). |
      | gateway\_port: 30845 | The port of the API gateway for your deployment. Do not set this port to 443 if setting up SSL.  If you are not implementing SSL, this is the port used to connect to Sisense. |
      | is\_ssl: false | For secure connections to Sisense, set this to **true** and see [Setting Up SSL for Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/setting-up-ssl-for-sisense-linux.md).  If you have not implemented SSL, set this to **false**. |
      | ssl\_key\_path: "" | If you connect to your server securely, enter the SSL keypath.  When SSL is defined, the Sisense API Gateway Port will be 443 and not the gateway\_port value. |
      | ssl\_cer\_path: "" | If you connect to your server securely, enter the SSL certificate path (.cer file). |
      | weave\_enabled: false | Set this to **true** if your cluster uses Azure or Google virtual machines, or any other instance in your deployment that does not support IP in the IP network protocol.  The default network plugin is Calico. Sisense supports the Weave network plugin for communication between nodes. |
      | new\_node: false | To add new nodes, set this to **true**.  You can add additional nodes if you have already provisioned Sisense and have a working cluster.  You must define the new nodes in the k8s\_nodes parameter, in addition to the existing nodes. Adding new nodes does not affect your existing nodes. |
      | remove\_node: false | To remove a node from your cluster, set this to **true**.  Enter the node to be removed in the value of the node\_to\_remove parameter. |
      | nodes\_to\_remove: "node4" | Enter the name of a node to be removed.  You can remove multiple nodes by entering a comma-separated list of nodes, for example: node\_1, node\_2.  **Note:**  You will need to update the`k8s_nodes`parameter if a node is removed. |
      | update\_k8s\_version: false | To update the Kubernetes version, set this to **true**. |
      | cni\_plugin: | Enables the user to set their preferred CNI (Container Network Interface) while deploying a new Kubernetes.  Valid values: calico (default), flannel  **Note:**   When update\_k8s\_version is set to true, you must set this to your currently existing CNI value. (You can find your CNI value with the command:`kubectl get pod -n kube-system | grep 'calico\|flannel'`. |
      | recover\_kubernetes: false | If one of your nodes is broken, set this to **true**. Sisense removes the node and recovers it. |
      | #http\_proxy: | (Optional) If you use a web proxy, enter the unsecured proxy value.  **Note:**  If your Linux system uses a proxy server for external traffic and no proxy for local traffic, you must complete the system configuration and Sisense configuration steps in [Configuring for Linux Installation on a Proxy, No Proxy System](https://docs.sisense.com/main/SisenseLinux/configuring-for-linux-installation-on-a-proxy-no-proxy-system.md) before initializing Sisense on your system. |
      | #https\_proxy: | (Optional) If you use a web proxy, entered the secured proxy value. |
      | #no\_proxy: | (Optional) If you use a web proxy, enter the addresses to exclude from your proxy. You can use commas to seperate multiple IP addresses. |
      | internal\_monitoring: true | When **true**, Sisense installs a Prometheus/Grafana/Flunetd dashboard.To disable a Prometheus-supported Grafana dashboard from monitoring your deployment, set this to **false**. See [Monitoring Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/monitoring-sisense-on-linux.md) and [Installing RKE with a Specified UID](https://docs.sisense.com/main/SisenseLinux/installing-rke-with-a-specified-uid.md). |
      | uninstall\_cluster: false | To remove Kubernetes infrastructure and Sisense services, set this to **true**. |
      | uninstall\_sisense: false | To uninstall Sisense services, but leave your Kubernetes infrastructure unchanged, set this to **true**. Only the Sisense application is removed.  This can be used if you need to remove Sisense from your own cloud-based cluster without impacting the cluster. |
      | remove\_user\_data: false | To delete all user data, set this to **true**.  This deletes your ElastiCube models, application database, message broker, and add-ons. |
      | signature\_validation: false | Enter **true** to enable [Image Signature Validation](https://docs.sisense.com/main/SisenseLinux/image-signature-validation.md). |
      | delete\_local\_images: false | For offline customers. Enter **true** for when uploading images to your private registry (command `bash ./installer/offline/offline_installer.sh upload ${CONFIG_FILE} <USERNAME>`), after each successful upload, it will delete the image from your local registry on your server and will also remove the `.tar` of that image from the installation dir in your local file system, thereby saving a lot of space on your server. |
   6. Run the configuration script.   
      `vim./sisense.sh cluster_config.yaml`  
      Your configuration settings are displayed with a message to confirm that you want to deploy Sisense with these settings.
   7. Enter **Yes** to confirm that you want to deploy Sisense.   
      Enter **No** to abort the deployment.   
      If there are any issues, you can view the installation logs as follows:

      vim[installation-dir]/sisense-ansible.log

   When the installation finishes, a list of endpoints are displayed for accessing Sisense and managing your deployment. The URLs are listed below. Additionally, you can run the following command to return the URL to access Sisense:

   vimkubectl cluster-info

   This command displays the URLs of your Sisense application. You can enter these addresses in your browser to access Sisense.

   To verify that all your services are running as expected, you can enter the Sisense URL with the port and /app/test concatenated to the end of the address in your browser. This displays the status of each of your services. For example:

   0.0.0.0:PORT/app/test

   To connect to Sisense, in your browser, enter the URL address into your browser:

   To see a list of endpoints in the multi-node cluster installation, connect to Sisense in your browser and enter the relevant command in your browser:

   - For non-secure connections:

     http://{IP}:30845/
   - For secure connections:

     https://{IP}/

   To connect to your Kubernetes dashboard, enter the following in your browser:

   https://{IP}:6443/api/v1/namespaces/kubesystem/services/https:kubernetes-dashboard:/proxy   
   https://{IP}:6443/api/v1/namespaces/kubesystem/services/https:kubernetes-dashboard:/proxy

   [Deployment on OpenShift](#)

   See [Installing Sisense on OpenShift](https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-openshift.md) to install Sisense on the OpenShift platform.

   If you have an OpenShift environment on AWS, Sisense has created a script you can use to prepare your environment, see [Preparing an OpenShift Environment](https://docs.sisense.com/main/SisenseLinux/preparing-an-openshift-environment.md).

   If you need to install OpenShift offline, see [Installing Sisense on OpenShift Offline](https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-openshift-offline.md).

   **Notes:**

   - Before you install Sisense, all Linux non-root users must have sudo permissions to initialize Sisense. Sisense services only run as part of the Sisense user and do not use Root user permissions. If you must install Sisense as a Root user, see [Sisense Service Permissions](https://docs.sisense.com/main/SisenseLinux/sisense-service-permissions.md).
   - Monitoring is **not** supported for OpenShift installations. If these parameters are included the configuration YAML file they **must be disabled**, (set to `false`). Please consider using OpenShift built-in monitoring tools instead.

   [Deploying on Cloud-Based Kubernetes](#)

   Sisense supports several cloud-based Kubernetes systems in which you can deploy Sisense Linux on your own cloud-based Kubernetes, including:
   - Amazon EKS
   - Google GKE
   - Microsoft AKS

   Sisense Linux can be deployed on each of these by configuring the cloud\_config.yaml file. For specific instructions, see:

   - [Deploying Sisense on Amazon EKS](https://docs.sisense.com/main/SisenseLinux/deploying-sisense-on-amazon-eks.md)
   - [Deploying Sisense on Google GKE](https://docs.sisense.com/main/SisenseLinux/deploying-sisense-on-google-gke.md)
   - [Deploying Sisense on Azure Kubernetes Service](https://docs.sisense.com/main/SisenseLinux/deploying-sisense-on-azure-kubernetes-service.md)
6. Once the installation is complete, some Sisense pods will remain in the Init state until the license activation. To activate the license, navigate to the Sisense web application URL (without extra paths such as */app/account/login*) in your browser and enter your license credentials.

For more information, watch this video about Installing Sisense:

**Tip:**

For more information, see:

- [Creating Data Groups](https://docs.sisense.com/main/SisenseLinux/creating-data-groups.md) for next steps
- On the Sisense Community site:

  - [Verifying Sisense Installation Completion - Analyzing Migration Pod Messages](https://community.sisense.com/t5/knowledge-base/verifying-sisense-installation-completion-analyzing-migration/ta-p/25518)
  - [Resolving installation error for Sisense - sisense-installer/bin/activate: no such file or directory](https://community.sisense.com/t5/knowledge-base/resolving-installation-error-for-sisense-sisense-installer-bin/ta-p/25519)
  - [Resolving Installation Failures with "Error occurred during validate\_ssl\_certs section"](https://community.sisense.com/t5/knowledge-base/resolving-installation-failures-with-quot-error-occurred-during/ta-p/22501)
  - [Installation fails with /bin/activate: No such file or directory](https://community.sisense.com/t5/knowledge-base/installation-fails-with-bin-activate-no-such-file-or-directory/ta-p/22500)