Skip to main content
Summation connects to Amazon Redshift using standard host, port, database, username, and password credentials. After the connection is saved, you can browse Redshift schemas and tables and add them as datasets.

​
What you’ll need

  • A reachable Redshift endpoint and port. Redshift Serverless defaults to port 5439. See Connecting to Amazon Redshift Serverless.
  • A database name.
  • A user with access to the schemas and tables you want exposed. The user needs USAGE on the schema and SELECT on the tables or views. See GRANT in the Redshift docs.
  • Network access from Summation to your Redshift endpoint.
Create a dedicated read-only Redshift user for Summation. This keeps queries auditable and prevents accidental writes from the connector.

​
Form fields

FieldRequiredStored asNotes
HostYesConfigRedshift endpoint host, e.g. cluster.example.us-west-2.redshift.amazonaws.com.
PortYesConfigDefault 5439.
DatabaseYesConfigRedshift database name.
UsernameYesConfigLogin user.
PasswordYesSecretPassword for the login user.
SSL ModeOptionalConfigDefault prefer. Use require or stricter when your Redshift endpoint requires TLS.
Root Certificate PathOptionalConfigPath to a CA bundle when using certificate verification.
Connection Pool SizeOptionalConfigMax concurrent connections from Summation. Default 10.

​
Setup SQL

Replace analytics with the schema you want Summation to read. 
CREATE USER summation PASSWORD '<strong-password>';

GRANT USAGE ON SCHEMA analytics TO summation;
GRANT SELECT ON ALL TABLES IN SCHEMA analytics TO summation;

ALTER DEFAULT PRIVILEGES IN SCHEMA analytics
  GRANT SELECT ON TABLES TO summation;

​
Adding datasets

After saving the connection, browse Redshift schemas and select tables or views. Source references use the Postgres-compatible form: 
postgres:public.orders

​
Common problems

Error or symptomLikely cause
connection refusedWrong host or port, or your network/firewall doesn’t allow traffic from Summation.
timeoutRedshift is private or behind a VPC path Summation cannot reach.
authentication failedWrong username or password.
permission deniedGrant USAGE on the schema and SELECT on the table or view.
Tables don’t appear in the browserThe user can connect to the database but lacks access to the schema or table metadata.