Redshift (Destination)

Loads data into Amazon Redshift using a staging location in S3 (COPY workflow).

Configuration

warehouse:
  kind: redshift
  database: analytics
  cluster_identifier: my-cluster
  schema: public
  region: us-east-1
  staging_s3_bucket: my-load-bucket
  staging_s3_prefix: "skippr/staging/"
  iam_role_arn: "arn:aws:iam::123456789012:role/RedshiftS3Role"

Field	Default	Description
database	(required)	Redshift database name
schema	public	Target schema
cluster_identifier		Provisioned cluster identifier
workgroup_name		Serverless workgroup (alternative to cluster)
db_user		Database user for COPY
region		AWS region
staging_s3_bucket		S3 bucket for staging files before COPY
staging_s3_prefix		Prefix inside the staging bucket
iam_role_arn		IAM role Redshift uses to read from S3

CLI

skippr connect warehouse redshift \
  --database analytics \
  --cluster-identifier my-cluster \
  --db-user admin \
  --schema public \
  --region us-east-1

Flag	Description
--database	Redshift database name
--cluster-identifier	Provisioned cluster ID (use this or --workgroup-name)
--workgroup-name	Serverless workgroup name (use this or --cluster-identifier)
--db-user	Database user (provisioned clusters)
--schema	Target schema (default: public)
--region	AWS region

Authentication uses the AWS default credential chain (env vars, instance profile, SSO).

CDC

Redshift supports CDC with staging-table MERGE semantics. Skippr automatically creates _skippr_order_token columns and tombstone tables.

See CDC Destinations -- Redshift for details.