Connecting Amazon Redshift to Sylvan allows Sylvan to tap into your query-ready datasets and power real-time, intelligent monitoring — without requiring you to move or duplicate your data.
Once connected, Sylvan can use its advanced analyzing capabilities, like anomaly detection and root cause analysis, to trigger smart workflows, surface insights, and help teams act faster and with greater confidence.
This guide provides instructions for both Redshift Serverless and Provisioned Cluster setups, helping you configure access and securely share the necessary details with Sylvan.
In this article we are going to cover the following topics:
In this article we are going to cover the following topics:
Information Needed to Set Up the Connection in Sylvan
Under the Connections page, you'll need to provide the following information:
Source Name: A custom name to identify this source in Sylvan.
Host: The public endpoint of your Redshift workgroup or cluster (Serverless or Provisioned). Do not use an internal or private hostname (e.g., anything ending in
.internalor resolving to a10.x.x.xaddress).Port: Automatically parsed from the Host input field.
Username & Password: Credentials for a Redshift user with read-only access to the tables/views Sylvan needs. We recommend creating a dedicated user for Sylvan. How to Create a Redshift User
Database Name: The name of the database Sylvan will access.
Connection Methods
Sylvan supports two methods to connect to your Redshift database:
Method 1: Direct Connection
Sylvan connects directly to your cluster's public endpoint.
Requirements:
Your cluster must be publicly accessible
Port 5439 must be open to Sylvan's IP:
34.123.149.4
¹ Enabling "publicly accessible" does not expose your database to the internet. Only traffic explicitly allowed through your VPC security group rules can reach the cluster. In this case, that means only Sylvan's IP address.
ℹ️ Firewall Settings (Direct Connection Only)
If your Redshift database is protected by a firewall and you're using the Direct Connection method, add an inbound rule allowing Sylvan's IP 34.123.149.4 on port 5439. This must be configured in your VPC Security Group in addition to enabling public accessibility.
Method 2: SSH Tunnel
Sylvan connects through an SSH bastion host in your VPC. Your Redshift cluster stays private with no public IP needed.
Requirements:
Provide the bastion host and port
Create a
sylvanuser on the bastion hostAdd Sylvan's public key to
~/.ssh/authorized_keys
📖 Learn more: Connect to Sylvan via SSH Tunnel
Step-by-Step Instructions for Redshift Serverless
👉🏻 Note: These instructions are for Direct Connection. If you're using SSH Tunnel, skip steps 1-2 and follow the SSH Tunnel guide instead.
1. Enable Public Access
Navigate to the Serverless Dashboard in the AWS Redshift UI
Go to Workgroups, then select the workgroup you want to connect to Sylvan
Under the Network and security section, click Edit
Check the box for Turn on publicly accessible
Click Save
⚠️ Note: If you encounter issues with public IPs being inaccessible, refer to AWS Documentation on Private and Public IP Access.
¹ Enabling "publicly accessible" does not expose your database to the internet. Only traffic explicitly allowed through your VPC security group rules can reach the cluster. In this case, that means only Sylvan's IP address.
2. Configure Your VPC Security Group
Open your VPC Security Group in the AWS console.
Add an inbound rule: Custom TCP, Port 5439, Source
34.123.149.4/32.Save the rule.
3. Retrieve the Workgroup Endpoint
In the Serverless Dashboard, go to Namespaces/Workgroups.
Locate the workgroup you wish to connect.
Copy the public endpoint and paste it into the Host field in Sylvan.
Ensure you are not using a private or internal hostname
4. Create a User with Appropriate Permissions
Follow the AWS guide to Create a New User in Redshift.
Assign this user read-only permissions for the tables or views Sylvan should access.
5. Find the Database Name
You can find it in the Serverless Dashboard under the Database tab of your namespace.
Step-by-Step Instructions for Redshift Provisioned Clusters
👉🏻 Note: These instructions are for Direct Connection. If you're using SSH Tunnel, skip steps 1-2 and follow the SSH Tunnel guide instead.
1. Enable Public Access
Navigate to the Provisioned Clusters Dashboard.
Select the cluster you want to connect to Sylvan.
Go to the Properties tab and find Network and security.
If Publicly accessible is set to "Disabled":
Click Edit.
Check the box for Turn on publicly accessible.
Click Save (the cluster may restart briefly).
2. Configure Your VPC Security Group
Open your VPC Security Group in the AWS console.
Add an inbound rule: Custom TCP, Port 5439, Source
34.123.149.4/32.Save the rule.
3. Retrieve the Cluster Endpoint
In the Cluster Dashboard, select your cluster.
Copy the public endpoint and paste it into the Host field in Sylvan.
Ensure you are not using a private or internal hostname (e.g.
data-rs-bi.internal.yourcompany.com).
4. Create a User with Appropriate Permissions
Follow the AWS guide to Create a New User in Redshift.
Assign this user read-only permissions for the tables or views Sylvan should access.
5. Find the Database Name
The database name is displayed in the Database section of your cluster details in the Redshift UI.
Troubleshooting Common Issues
Connection Refused
Ensure that Publicly Accessible is enabled for your workgroup/cluster (if using Direct Connection).
Verify that your VPC Security Group has an inbound rule allowing
34.123.149.4/32on port 5439 (if using Direct Connection).If your endpoint resolves to a private IP (e.g. a 10.x.x.x address), Sylvan cannot reach your cluster even with the IP whitelisted — ensure you are using the public endpoint.
Refer to this AWS Knowledge Base Article for additional guidance.
If using SSH Tunnel, verify your bastion host is accessible and the
sylvanuser is properly configured
Firewall Settings
If your Redshift database is protected by a firewall, ensure you allow access from Sylvan’s IP address: 34.123.149.4