Installation on cloud provider
Last updated
Last updated
This section applies to installing Dash Enterprise on a single server on a supported cloud provider. For installing the Kubernetes version of the software, see Dash Enterprise Kubernetes installation using cloud provider's Kubernetes cluster.
Currently we support a simplified installation on Amazon Web Services using an EC2 virtual server and a custom AMI (similar support for other cloud providers is in development). To install on a different cloud provider, simply provision a compute instance that meets our requirements, then follow the instructions in Dash Enterprise Single Server: On-Premise Installation on Own Server.
With the current release, your cloud instance must be able to access the Internet, either directly or via a proxy, to use our automated installation process. If your instance does not have Internet access, skip ahead to Dash Enterprise Single Server: fully offline installation.
Provision a Linux VM equal to D4s v3 in size and compute power (or larger), then proceed to section On-premise installation on own server.
Provision a Linux VM equal to n1-standard-8 in size and compute power (or larger), then proceed to section On-premise installation on own server.
Dash Enterprise can be installed by launching an Amazon Machine Image as follows:
1 - Log into your AWS console and visit the EC2 Management Console in the region of your choice; in this example, we have chosen the ca-central-1 region:
2 - Click Launch Instance
3 - At Step 1: Choose an Amazon Machine Image (AMI), select Community AMIs (circle 1) from the menu on the left, then enter plotly in the search box (circle 2):
4 - Ensure the ID of the AMI (circle 3) matches the ID in the below table for the region you’re using:
Region
AMI ID
eu-north-1
ami-03f3c524a4e11df67
ap-south-1
ami-02e15d1d6d7659d25
eu-west-3
ami-006cd3ed68cc5537d
eu-west-2
ami-08e1e4d90996771ac
eu-west-1
ami-01186202a2a7f187e
ap-northeast-3
ami-041c669126c7de130
ap-northeast-2
ami-0ba72b5a622c20acd
ap-northeast-1
ami-0a33702485dc20f89
sa-east-1
ami-0e62fcd37a515e265
ca-central-1
ami-09d386c9765566095
ap-southeast-1
ami-0920462e2e649d20f
ap-southeast-2
ami-03674ba6d83d70000
eu-central-1
ami-05c4b86250aff5c67
us-east-1
ami-0ff039b741f6dbccc
us-east-2
ami-0d4ee6e74242f698e
us-west-1
ami-09de668901a669dfc
us-west-2
ami-071f5a9a3e80cbb9c
5 - After verifying the AMI ID, click Select to choose the AMI
6 - In Step 2: Choose an Instance Type, select an appropriate instance type and click Next: Configure Instance Details
t2.2xlarge is a good option, but you can choose a larger instance type if you want higher performance
7 - On Step 3: Configure Instance Details, set Auto-assign public IP to Disable, then click Next: Add Storage
8 - On Step 4: Add Storage, set the Size (GiB) of the root volume, then click Next: Add Tags
We recommend 2000 GiB
This number may be increased or decreased depending on the size of the active team, but should never be less than 200 GiB
We currently do not support splitting your server’s directory structure across multiple block devices; please add only one storage volume of the required size
9 - On Step 5: Add Tags, you may optionally add a Name tag of plotly-on-premise and any other tags you require for your organization purposes
When done, click Next: Configure Security Group
10 - On Step 6: Configure Security Group, select Create a new security group, give it a descriptive name such as plotly-on-premise, and configure entries as below:
The Custom TCP 3022 rule is only needed for Dash Enterprise; all others are required
To restrict access to Dash Enterprise to a single IP address (or range of IPs) replace the default Source values (0.0.0.0/0, ::/0) with the address or range
Once you have configured the security group, click Review and Launch
11 - On Step 7: Review Instance Launch, carefully review the information and especially confirm that the security groups match the ones shown below:
If any information is incorrect, use the Edit links to go back and correct it.
12 - After verifying, click Launch and choose a key pair you have access to, or create a new key pair and download it * This step is extremely important! Without this key pair, you will not be able to SSH into your server and the key pair is very difficult to reset.
13 - On the Launch Status screen, click View Instances at the bottom right
14 - Associate an Elastic IP with your instance (see Associate an Elastic IP)
To ensure your instance’s IP address does not change when the instance is rebooted or undergoes other maintenance, associate an Elastic IP address with the instance as follows:
1 - In your AWS console, select Elastic IPs from the menu on the left
2 - Select Allocate new address, leave the Scope set to VPC, then choose Allocate
3 - On the New address request succeeded screen, note the new address (in this case 52.60.140.183) and then click the address
4 - In the Elastic IPs screen, ensure your new IP address is selected, then click Actions > Associate address
5 - Click Select an instance and choose your new instance from the list
6 - Click the Associate button at the bottom right, then Close
Your instance is now ready for you to upload your license and configure Dash Enterprise. If your instance uses a proxy to access the Internet, see Configuring a proxy. Otherwise, skip to Configuration to continue.
To administer your instance via SSH, you may log in using the plotly username and the SSH key you selected or uploaded when launching your new instance.
If your system requires a proxy to access the Internet,configure as follows:
1 - SSH into the running instance
2 - Run the Plotly installation script:
3 - When asked if your machine requires a proxy to access the internet, enter y and provide your proxy details when prompted
4 - Once this script is complete, proceed with the instructions in Configuration
If your proxy credentials are rotated periodically, Dash Enterprise can still use your proxy, but please contact Plotly support for additional instructions.
