Setting up the Cloud Environment

Applicable to Sisense on Linux and Microsoft Windows

While Sisense configures your cloud environment, there are a few steps you must complete to manage Sisense. The Sisense Cloud Operations team will assist you to complete the following tasks described below.

Access to the Cloud Environment

Based on the details provided in the Cloud Setup Form, the Sisense Cloud Operations Team deploys the cloud environment. How your users access the environment is described in the diagram below.

All users can access dashboards and Sisense via secure HTTPS from any location. The default Sisense site is https://<customer_name>.sisense.com. Should a custom domain be required, Sisense supports custom URLs using SSL certificates provided by you, as described here.

If necessary, you can access the Desktop ElastiCube Manager as described in Accessing the Desktop ElastiCube Manager.

Data Transfer

In some cases, you may want to transfer data to Sisense, for example, when uploading Excel files or customized add-ons.

Sisense supports the following data source connections to connect to the Sisense application database:

  1. Direct connection to a database with or without SSL
    If selected, you will provide Sisense with your public/external IP and port of the database. If SSL encryption is required, you will provide an SSL certificate and send it to Sisense
  2. Site-2-site VPN (IPSec) tunnel
    If you choose this option, Site-2-site VPN, Sisense will create a dual-tunnel AWS VPN. You must configure a firewall to connect to the database via internal IP routing based on the AWS configuration instructions provided by Sisense.
  3. SSH Tunnel
    The SSH server should be set up on the database server or via a bastion gateway.
  4. VPC Peering
    For databases deployed on an AWS VPC, you need to provide the VPC details. Once the cloud environment is deployed, Sisense will issue a peering request or, alternatively, you can issue a peering request from your VPC.
  5. Access to AWS RDS, Athena, etc. with or without SSL
  6. Secure FTPS as described here: Transferring Files to Sisense Cloud.
  7. Sisense Customer Data Proxy
    If none of the above methods is applicable, the Sisense Customer Data Proxy (CDP) can be deployed on a virtual machine behind a firewall to locally connect to your data source(s). The CDP is an OVA VM image to be deployed within your network where it should have at least one interface on a subnet with the source DB, and at least one interface routable to the internet, and open for outgoing connections on port TCP 22. The CDP maintains the outbound connection to the Sisense cloud to transfer the data via an encrypted SSH tunnel. The CDP supports multiple data sources within your network. For a detailed description of the CDP, click here.

Configuring your Network

Sisense’s Cloud Managed Service is deployed on secure AWS server(s) specifically dedicated to you. Access to the server is restricted to designated applications only. No other programs/processes can be run on the Sisense Server.

To connect the Sisense Managed Cloud Service to your database, the following ports should be open for outbound traffic:

The relevant IP addresses are provided to you by Sisense from the Sisense Cloud Operations Team.

After setting up your cloud environment, Sisense will contact you to schedule an online Cloud Access Verification Session.

Optional Configuration

Custom DNS: Review to implement a rebranded URL for Sisense.

Introduction to SSO: Review to implement SSO in your cloud environment.

Connecting to JDBC: Review to connect to various data sources with the Sisense JDBC connector.