Skip to content
DataSquaresDocs
datasquares.aiSign inStart free

Connect DataData Warehouses

Redshift

You connect Redshift from the DataSquares connection wizard.

  1. In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.

  2. Pick Redshift on that page (search or browse by category).

  3. Fill in the connection details below, then test the connection and save.

Connection details

Section titled “Connection details”
Field What to enter
Host The hostname or IP address of your Redshift server.
Port Prefilled with 5439 (the Redshift default) — change it if your server listens elsewhere.
Database The database to connect to.
Username / Password Credentials for a user with read access to the tables you want to analyze.
TLS On by default: Use SSL/TLS encryption connects encrypted and verifies the server certificate. Tick Trust self-signed certificate for a private CA; turn TLS off only for a server that has none.

Grant the connection user read-only access — DataSquares only ever reads from your source.

Grant read-only access

Section titled “Grant read-only access”
CREATE USER datasquares PASSWORD '********';
GRANT USAGE ON SCHEMA public TO datasquares;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO datasquares;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO datasquares;

Reachability

Section titled “Reachability”

Redshift clusters are VPC-resident: mark the cluster publicly accessible and allowlist the DataSquares server’s IP in its security group. A private route does not help — DataSquares refuses private addresses by design (see Troubleshooting). The endpoint host comes from the cluster’s details page; the default port is 5439.

Common errors

Section titled “Common errors”

Test Connection shows a short summary, such as Authentication failed — check the username and password. The text below is what the database itself reports, for example in the SQL editor.

Error Cause / fix
timeout security group doesn’t allow the DataSquares IP on 5439, or the cluster isn’t publicly accessible
permission denied for schema missing USAGE on the schema (a common Redshift trip-up — SELECT alone isn’t enough)
Section titled “Related”