AWS Redshift integration

Data warehouse: clusters, snapshots, SQL execution via Data API

Help CentreConnectors

Overview

Amazon Redshift is AWS's petabyte-scale columnar data warehouse. The Automize Redshift connector covers cluster management, snapshots, and SQL execution via the Redshift Data API (no JDBC/ODBC required).

  • Regions: Regional. Clusters live in one region.
  • Plans: Provisioned clusters (RA3 + DC2 node types) or Serverless. Reserved instances for steady workloads.

Setting up the connection

Auth type: aws_sigv4.

  1. AWS IAM → user + AmazonRedshiftFullAccess + AmazonRedshiftDataFullAccess.
  2. Cluster needs a SecretsManager secret OR DB user creds for the Data API.
  3. In Automize → Settings → Connectors → AWS Redshift. Paste keys + region.

Find your credentials at https://us-east-1.console.aws.amazon.com/iam/home.


Rate limits

Data API throttles at ~10 concurrent statements per cluster. Cluster management APIs at ~5 TPS.


Data model

Compute + storage:

    Cluster (multi-node) ─── Databases ─── Schemas ─── Tables ─── Rows
                        └─ Snapshots (manual + automated)
    Data API: REST-based query execution (no JDBC driver needed)

Available operations

17 operations available. Click any row to jump to its detail.

OperationCategoryWhat it does
Batch Execute SQLGeneralExecute multiple SQL statements
Create ClusterGeneralCreate a new Redshift cluster
Create SnapshotGeneralCreate a cluster snapshot
Delete ClusterGeneralDelete a Redshift cluster
Delete SnapshotGeneralDelete a cluster snapshot
Describe SnapshotsGeneralList cluster snapshots
Describe ClustersGeneralList Redshift clusters
Describe StatementGeneralGet status of a SQL statement
Execute SQLGeneralExecute a SQL statement via the Data API
Get Statement ResultGeneralGet results of a completed SQL statement
List StatementsGeneralList recent SQL statements
Modify ClusterGeneralModify cluster settings
Pause ClusterGeneralPause a cluster
Reboot ClusterGeneralReboot a cluster
Resize ClusterGeneralResize a cluster
Restore from SnapshotGeneralRestore a cluster from a snapshot
Resume ClusterGeneralResume a paused cluster

Operations

Batch Execute SQL

Execute multiple SQL statements

No input parameters.


Create Cluster

Create a new Redshift cluster

No input parameters.

Tips

  • Heavy – Provisioned cluster. NodeType + NumberOfNodes + MasterUsername + DBName.
  • Takes 10-20 min to provision. For Serverless use create-namespace (not exposed here).

Create Snapshot

Create a cluster snapshot

No input parameters.


Delete Cluster

Delete a Redshift cluster

No input parameters.


Delete Snapshot

Delete a cluster snapshot

No input parameters.


Describe Snapshots

List cluster snapshots

No input parameters.


Describe Clusters

List Redshift clusters

No input parameters.

Tips

  • Filter by ClusterIdentifier. Returns endpoint + node type + status.

Describe Statement

Get status of a SQL statement

No input parameters.

Tips

  • Status: SUBMITTED, PICKED, STARTED, FINISHED, FAILED, ABORTED.

Execute SQL

Execute a SQL statement via the Data API

No input parameters.

Tips

  • SQL via Data API. Async – returns statementId.
  • ClusterIdentifier + Database + DbUser (or SecretArn) + Sql.
  • Poll Describe Statement for status.

Get Statement Result

Get results of a completed SQL statement

No input parameters.

Tips

  • Returns columnar results. Pages via NextToken.

List Statements

List recent SQL statements

No input parameters.


Modify Cluster

Modify cluster settings

No input parameters.


Pause Cluster

Pause a cluster

No input parameters.

Tips

  • Stops compute, retains storage. Cheaper. Use Resume Cluster to restart.

Reboot Cluster

Reboot a cluster

No input parameters.


Resize Cluster

Resize a cluster

No input parameters.


Restore from Snapshot

Restore a cluster from a snapshot

No input parameters.


Resume Cluster

Resume a paused cluster

No input parameters.

Tips

  • Restart paused cluster. ~5 min to become available.

FAQ

Serverless vs Provisioned?
Serverless auto-scales + pay-per-RPU-hour, great for spiky workloads. Provisioned cheaper for steady high utilisation.
Why is my SQL taking forever?
Compute capacity bound. Check WLM queue, consider scaling, or use SORTKEY/DISTKEY tuning.

Related connectors

See it working on your own data

Everything documented here ships with the platform – try the document tools free, or go live in 7 days.