Redshift Connection

Redshift Connection Skill

On Entry

Tell the user:

Setting up Redshift connection — I'll configure and test a connection to your source Redshift cluster. I'll need some connection details from you shortly.

Prerequisites

• Network access to the Redshift cluster or serverless endpoint
• For IAM auth: AWS credentials (access key ID + secret access key)
• For standard auth: Redshift username and password
• The scai CLI installed and available

Required Connection Details

IAM Provisioned Cluster (Recommended)

IAM Serverless

Standard Auth

Workflow

Step 1: Ask How to Provide Credentials

Ask the user:

"I need the following to connect to Redshift:

• Cluster ID or Workgroup (depending on auth method)
• Database name
• AWS credentials (for IAM auth) or username/password (for standard auth)

How would you like to provide these?"

Options:

1. 1Password - Credentials stored in 1Password vault
2. Enter manually - Provide values interactively

Step 2: Route Based on Answer

Step 3: Add the Connection (Manual Entry)

Interactive mode (recommended):

scai connection add-redshift

IAM Provisioned Cluster (inline):

scai connection add-redshift \
  -c <CONNECTION_NAME> \
  --auth iam-provisioned-cluster \
  --user <USER> \
  --cluster-id <CLUSTER_ID> \
  --database <DATABASE> \
  --region <REGION> \
  --access-key-id <ACCESS_KEY_ID> \
  --secret-access-key <SECRET_ACCESS_KEY>

IAM Serverless (inline):

scai connection add-redshift \
  -c <CONNECTION_NAME> \
  --auth iam-serverless \
  --workgroup <WORKGROUP> \
  --database <DATABASE> \
  --region <REGION> \
  --access-key-id <ACCESS_KEY_ID> \
  --secret-access-key <SECRET_ACCESS_KEY>

Standard auth (inline):

scai connection add-redshift \
  -c <CONNECTION_NAME> \
  --auth standard \
  --host <HOST> \
  --port 5439 \
  --database <DATABASE> \
  --user <USERNAME> \
  --password <PASSWORD>

Step 4: Save and Test Source Connection

Call the configure tool with source_connection set to <CONNECTION_NAME>. The MCP server runs scai connection test internally and only persists the connection if the test passes.

• On success: the response includes connection_test: ok.
• On failure: the tool returns an error containing the scai message. Surface it to the user, help them fix the issue, then re-run configure(source_connection=<CONNECTION_NAME>). See ./references/REFERENCE.md for detailed troubleshooting.

Common errors:

CHECKPOINT

Confirm with user:

• configure returned connection_test: ok
• Connection appears in scai connection list -l redshift --json
• Source connection saved to session config

On Completion

After the CHECKPOINT passes, tell the user:

Connection configured — Successfully connected to Redshift using connection <connection_name>.

Then return to the calling skill.

Security Rules

• NEVER log or display secrets (passwords, secret access keys) in plain text
• NEVER include secrets in command-line arguments that might be logged
• Use interactive mode or credential managers (1Password) to avoid secret exposure

Quick Reference