Welcome to the Redash Deployment Guide for AWS Integration! Redash lets you connect to any data source, build queries, visualize data, and share insights with your team. This guide walks you through deploying Redash on AWS using our AMI and CloudFormation template, configuring email, inviting users, and operating it with best practices.

Prerequisites

Before you get started with the Redash AMI, ensure you have the following prerequisites:

Launching the AMI

Step 1: Find and Select 'Redash' AMI

  1. Log in to your AWS Management Console.
  2. Navigate to the 'Redash' product in AWS Marketplace.

Step 2: Initial Setup & Configuration

  1. Click the "Continue to Subscribe" button.
  2. Accept the terms and click "Continue to Configuration".

Step 3: Launching the Instance

  1. Select the "CloudFormation" fulfillment option and choose your preferred region, then click "Continue to Launch".
  2. From the action menu, select "Launch CloudFormation" and click "Launch".

Create CloudFormation Stack

Step 1: Create stack

  1. Ensure the "Template is ready" option is selected under "Prepare template".
  2. Click "Next".

Step 2: Specify stack options

  1. Provide a unique "Stack name".
  2. Provide the "Admin Email" for SSL generation.
  3. For "DeploymentName", enter a name of your choice.
  4. Provide a public domain name for "DomainName" (SSL will be set up manually after deployment using the provided script).
  5. Choose an instance type, "InstanceType" (Recommended: t3.small).
  6. Select your preferred "keyName".
  7. Set "SSHLocation" as "0.0.0.0/0".
  8. Keep "SubnetCidrBlock" as "10.0.0.0/24".
  9. Keep "VpcCidrBlock" as "10.0.0.0/16".
  10. Click "Next".

Step 3: Configure stack options

  1. Choose "Roll back all stack resources" and "Delete all newly created resources" under the "Stack failure options" section.
  2. Click "Next".

Step 4: Review

  1. Review and verify the details you've entered.
  2. Redash Developer Guide
  3. Tick the box that says, "I acknowledge that AWS CloudFormation might create IAM resources with custom names".
  4. Redash Developer Guide
  5. Click "Submit".

Afterward, you'll be directed to the CloudFormation stacks page.

Please wait for 5-10 minutes until the stack has been successfully created.

Redash Developer Guide

Update DNS

Step 1: Copy IP Address

Copy the public IP labeled "PublicIp" in the "Outputs" tab.

Redash Developer Guide

Step 2: Update DNS

  1. Go to AWS Route 53 and navigate to "Hosted Zones".
  2. Click Create record.
  3. Redash Developer Guide - Update DNS
  4. Add record name and paste the copied "PublicIp" into the "value" textbox.
  5. Click "Save".

Access Redash

You can access the Redash dashboard using the "DashboardUrl" or "DashboardUrlIp" provided in the "Outputs" tab. Proceed to create the initial Admin account; all subsequent users can be managed through the Redash Settings panel.

Access Redash

(If you encounter a "502 Bad Gateway" error, please wait about 5 minutes and then refresh the page.)

Redash initial screen Redash home

Generate SSL Manually

Redash will automatically try to set up SSL when a Route53-hosted domain is provided. If it fails, follow these steps to generate SSL manually.

Step 1: Copy IP Address

Proceed with the instructions outlined in the above "Update DNS" section, if you have not already done so.

Copy the Public IP address indicated as "PublicIp" in the "Outputs" tab.

Redash Developer Guide - Update DNS

Step 2: Log in to the server

  1. Open the terminal and go to the directory where your private key is located.
  2. Paste the following command into your terminal and press Enter:
ssh -i <your key name> ubuntu@<Public IP address>
  1. Type "yes" and press Enter. This will log you into the server.
Redash Developer Guide - Update DNS

Step 3: Generate SSL Certificate

Run the SSL generation script. The Admin Email is required for generating SSL certificates.

sudo /root/certificate_generate_standalone.sh

Check Server Logs

Step 1: Log in to the server

  1. Open the terminal and go to the directory where your private key is located.
  2. Paste the following command into your terminal and press Enter:
ssh -i <your key name> ubuntu@<Public IP address>
SSH to server
  1. Type "yes" and press Enter. This will log you into the server.

Step 2: Check the logs

sudo docker ps
sudo docker logs (container_id or container_name)
Containers list

Email Configuration

Configure SMTP settings to enable email invitations and alerts. Edit the environment file with your SMTP provider details as shown below.

Email configuration

Step 4: Apply Changes

After updating the email configuration, apply the changes by restarting the services:

cd /opt/redash
docker-compose down
docker-compose up -d

Email Sent and Invite Others

Once email is configured, you can invite teammates from the Redash Settings → Users section.

Email sent Invite users

Shutting Down Redash

  1. Click the link labeled "Instance" in the "Resources" tab to access the EC2 instance; you will be directed to the Redash instance in EC2.
  2. Go to instance
  3. Stop the instance by selecting the checkbox and click "Stop instance" from the "Instance state" dropdown. You can restart the instance at your convenience by selecting "Start instance".
  4. Stop instance

Remove Redash

Delete the stack that has been created in the AWS Management Console under 'CloudFormation Stacks' by clicking the 'Delete' button.

Upgrades

When there is an upgrade, we will update the product with a newer version. You can check the product version in AWS Marketplace. If a newer version is available, you can remove the previous version and launch the product again using the newer version. Remember to back up necessary server data before removing.

Troubleshoot

  1. If you face the following error, please follow https://meetrix.io/articles/how-to-increase-aws-quota/ blog to increase vCPU quota.
  2. Quota error
  3. If you face the following error (do not have sufficient <instance_type> capacity...) while creating the stack, try changing the region or try creating the stack at a later time.
  4. Insufficient capacity
  5. Check disk usage to ensure the instance storage is not full:
  • Log into the server and run the below command
df -h
Disk usage

If the root volume is between 90–100%, increase the EBS volume following AWS documentation. Then reboot the instance and restart the web server.

Conclusion

The Meetrix Redash Deployment Guide helps you set up Redash on AWS quickly and securely. Whether you're a DevOps engineer or administrator, this guide provides step-by-step instructions to deploy Redash in a scalable and reliable way.

Technical Support

Reach out to Meetrix Support (aws@meetrix.io) for assistance with Redash issues.