TVL Managed Superset
Get started

Connect Amazon Redshift to Apache Superset 2026

Tutorial to connect Amazon Redshift to Apache Superset: driver, URI, IAM auth, optimization, costs.

· Tuvalu Tech OÜ

Amazon Redshift remains a major cloud data warehouse in 2026, particularly with all-in AWS organizations. Connecting Apache Superset to Redshift requires the right driver and some specific optimizations. This guide details the procedure for 2026.

1. Prerequisites

  • An accessible Superset instance;
  • A Redshift cluster or Redshift Serverless;
  • A Redshift read-only account;
  • The sqlalchemy-redshift and redshift-connector drivers installed.

If you want a ready instance, TVL Managed Superset includes Redshift drivers by default.

2. Prepare Redshift

-- Create a dedicated user and schema
CREATE USER superset_reader WITH PASSWORD 'XXX';
GRANT USAGE ON SCHEMA public TO superset_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO superset_reader;
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT ON TABLES TO superset_reader;

3. Build the URI

redshift+redshift_connector://<user>:<password>@<cluster>.<region>.redshift.amazonaws.com:5439/<database>

With IAM auth (recommended for production):

redshift+redshift_connector://<cluster>.<region>.redshift.amazonaws.com:5439/<database>?iam=true&cluster_identifier=<cluster>&db_user=superset_reader

4. Add to Superset

  1. UI → Settings → Database Connections → + Database;
  2. Type: Amazon Redshift;
  3. Paste the URI;
  4. Test → Save.

5. Optimize for performance

Redshift is optimized for massive aggregations. Best practices:

  • DISTKEY on the main join column;
  • SORTKEY on time filter columns;
  • Regular VACUUM + ANALYZE;
  • Aggressive Superset cache (24h on stable dashboards);
  • Concurrency Scaling enabled for load peaks.

This configuration is applied by default on TVL Managed Superset, which follows community best practices.

6. Optimize costs

  • Redshift Serverless: pay-per-use billing, ideal for irregular analytics;
  • Pause/Resume on provisioned clusters outside business hours;
  • Federated Queries Redshift to S3 rather than loading TBs;
  • Materialized views for frequent aggregations.

7. Security

  • Private VPC Redshift, Superset access via VPC peering or VPN;
  • IAM roles instead of static credentials;
  • Audit logs Redshift enabled (STL_QUERY);
  • Encryption at-rest enabled by default.

8. Common pitfalls

  • SSL handshake: Redshift requires SSL by default, add ?sslmode=require;
  • Quote casing: Redshift is case-sensitive on quoted identifiers;
  • Concurrency limits: 50 concurrent queries default, monitor;
  • Initial latency: a paused cluster takes 30-60s to resume.

9. Conclusion

Redshift + Apache Superset is a robust combo for AWS-centric analytics. For similar use cases outside AWS, consider Snowflake (multi-cloud) or ClickHouse (open source). Redshift Serverless makes billing predictable for irregular workloads.

Want the benefits of Apache Superset without the friction of installation and maintenance? Deploy your instance in 3 clicks with TVL Managed Superset, hosted in Europe (OVHcloud, Roubaix, France).

For more: connect Snowflake, connect BigQuery, connect ClickHouse.