Redshift

Write data to an Amazon Redshift table using staging tables and MERGE. Use SignalSmith to materialize model results or enriched data into Redshift.

Prerequisites

  • An Amazon Redshift cluster or Redshift Serverless workgroup
  • A database user with CREATE TABLE, INSERT, UPDATE, and DELETE privileges
  • Network connectivity between SignalSmith and the Redshift cluster endpoint

Authentication

Redshift uses Username & Password authentication.

  1. Enter the Redshift Username and Password in SignalSmith

Configuration

FieldTypeRequiredDescription
HostTextYesRedshift cluster endpoint hostname (e.g., my-cluster.abc123.us-east-1.redshift.amazonaws.com)
PortNumberNoServer port. Default: 5439
DatabaseTextYesDatabase name (e.g., dev)
SSL ModeSelectNoSSL mode: Require, Verify CA, or Disable. Default: Require

Target Settings

FieldTypeRequiredDescription
SchemaTextYesDatabase schema to write to. Default: public
TableTextYesTarget table name

Supported Operations

Sync Modes: Upsert, Insert, Update, Mirror

Audience Sync Modes: Add, Remove, Mirror, Upsert

Features

  • Field Mapping: Yes
  • Schema Introspection: Yes — SignalSmith reads column metadata from Redshift’s information_schema

How It Works

SignalSmith uses staging tables and MERGE for efficient bulk operations:

  1. Data is loaded into a temporary staging table
  2. A MERGE statement is executed against the target table
  3. The staging table is dropped after the sync

Troubleshooting

Connection failed

Verify the cluster endpoint, port, and database name. Ensure the Redshift cluster is publicly accessible or that the network allows connections from SignalSmith.

Insufficient privileges

The user needs USAGE on the schema, and CREATE, INSERT, UPDATE, DELETE privileges on tables.

Cluster paused

If the Redshift cluster is paused, it must be resumed before syncs can run. Redshift Serverless workgroups resume automatically.

SSL required

Amazon Redshift typically requires SSL. Set SSL Mode to Require or Verify CA.