Linking Redshift as a Source
This guide walks through connecting a Redshift cluster to Actioneer. The setup creates a dedicated database user withSELECT-only permissions on the schemas you specify.
| Prerequisites | AWS account with a Redshift cluster, Actioneer account |
| Access granted | SELECT queries on specified schemas |
| Estimated time | ~20 minutes |
| Actioneer IP | 35.244.14.238 |
Actioneer cannot insert, update, delete, or modify any data, tables, or cluster settings.
Locate your Redshift cluster endpoint and database name
Three values are needed from the AWS Console.
- Sign in at console.aws.amazon.com and open the Amazon Redshift service.
- Click Clusters in the left sidebar and select your cluster.
- On the General information tab, copy the Endpoint. It follows the format
my-cluster.abc123.us-east-1.redshift.amazonaws.com:5439. The address before the colon is the Host. The number after the colon is the Port. Always use the port shown in your endpoint —5439is the AWS default, but it is not guaranteed. - Note the Database name shown on the same page (e.g.,
analytics).
| Field | Location | Value Example |
|---|---|---|
| Host | Cluster endpoint (without port) | my-cluster.abc123.us-east-1.redshift.amazonaws.com |
| Port | Cluster endpoint (after the colon) | 5439 |
| Database | General information tab | analytics |
Create a read-only database user
Connect to your Redshift cluster using a SQL client (Redshift Query Editor, DBeaver, or psql) and run the following. Replace
YOUR_SCHEMA with the schema Actioneer should query.Replace
YOUR_SCHEMA with your actual schema name (e.g., public or reporting). Run the GRANT statements for each schema Actioneer should access.Allow Actioneer's IP address
Redshift clusters are typically inside a VPC. Actioneer needs an inbound rule on the cluster’s security group to connect.
- In the AWS Console, open Amazon Redshift and select your cluster.
- On the Properties tab, under Network and security, click the linked VPC security group.
- Click Inbound rules → Edit inbound rules.
- Add a rule: Type = Custom TCP, Port = the port from Step 1, Source = Custom →
35.244.14.238/32. - Click Save rules.
Connect Redshift in Actioneer
- In Actioneer, click Data in the left sidebar.
- Select Amazon Redshift from the list of data sources.
- When prompted, select Direct Connection.
- Complete the connection form:
| Field | Value |
|---|---|
| Connection Name | A descriptive label, e.g. Production Redshift |
| Host | From Step 1 — cluster endpoint without the port |
| Port | From Step 1 |
| Database Name | From Step 1 (e.g., analytics) |
| Username | actioneer_readonly |
| Password | The password set in Step 2 |
| SSH Tunnel | Optional — enable to connect through a bastion host if your cluster is not publicly accessible |
- Click Connect.
Common questions
Can Actioneer modify data in Redshift?
Can Actioneer modify data in Redshift?
No. The
actioneer_readonly user holds only SELECT and USAGE grants. It cannot insert, update, delete, or drop any objects in your cluster.How does Actioneer protect credentials?
How does Actioneer protect credentials?
All credentials are encrypted at rest with AES-256 and encrypted in transit with TLS 1.3. They are never stored in plain text or logged. Actioneer is SOC 2 Type II certified, ISO 27001 certified (audited by Schellman), and GDPR compliant.
Need a hand?
Stuck on a step or running into an error? Reach out at connect@actioneer.com.