Dash Enterprise Administration
4.1.3
4.1.3
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
      • VMware Edition installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise only instance
      • Dash Enterprise and Chart Studio Enterprise instance
    • After the Upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page
  • Initial consideration
  • Port setup
  • Listener setup
  • Domain (DNS) setup

Was this helpful?

  1. Advanced Configuration

Load balancer configuration

This guide is for Dash Enterprise Single Server only. Dash Enterprise Kubernetes (DEK) does not support manually-configured load balancers. DEK manages its own load balancer service as part of installation and this is not configurable.

This guide works for any type of load balancer (LB). This includes Classic Load Balancers (CLB), Elastic Load Balancers (ELB), Application Load Balancers (ALB), and Network Load Balancers (NLB).

Configuring an external load balancer is not necessary to run Dash Enterprise. Dash Enterprise Single Server provides SSL termination and network load balancing of Dash apps using its built-in NGINX and HAProxy services. It is not possible to Load Balance between multiple instances of Dash Enterprise Single Server and so adding an external Load Balancer will not improve performance of your Dash apps. However you may consider using an external Load Balancer to enable features like Web Application Firewall (WAF).

Initial consideration

If using Dash Enterprise Single Server behind a load balancer, the LB will need to be configured to pass requests to the server.

These instructions assume you are using a Load Balancer (LB) on Amazon Web Services. To configure a different type of load balancer, please consult the documentation for your load balancer.

Port setup

The following ports must be opened on the LB and the LB target instance:

  • 443 (HTTPS)

  • 80 (HTTP)

    • This port is optional, as all requests are made over HTTPS

    • Enabling port 80 will allow Dash Enterprise to automatically redirect requests made on HTTP to HTTPS

  • 8800 (Server Manager)

  • 3022 (SSH connections to Dash Enterprise)

    • You cannot use standard SSH port 22 for this unless you disable SSH on the server, which we do not recommend

Listener setup

Configure listeners on ports 443, 80, and 3022 to point to instance ports 443, 80, and 3022, respectively.

Domain (DNS) setup

The Dash Enterprise domain name needs to point to the LB DNS name assigned by AWS.

For example, if:

  • The Dash Enterprise domain name is dash.your-company.com

  • The DNS name of your LB assigned by AWS is test.us-east-1.elb.amazonaws.com

Then, you need to set a CNAME as follows:

PreviousDash Enterprise KubernetesNextReverse proxy setup instructions

Last updated 3 years ago

Was this helpful?