Skip to main content
HTTP API connector An HTTP API described by an OpenAPI spec, not an MCP server. Calls go through xpander’s function endpoint https://functions.xpander.ai/aws-redshift, which fronts the AWS Redshift API, and carry a signature from the AWS Operator’s IAM role in your cluster, so there is no key to paste.

What the skill can do

API connector: 9 actions, as they appear in the skill panel. 9 of them create, change or delete something in AWS Redshift; mark those under These actions need approval when you add the skill to an agent.
  • Table inspection (3): Schema Browse List Tables In Schema, Inspect Get Sample Rows From Table, Inspect Get Table Column Schema
  • Result pagination (2): Query Run Execute Sql Statement, Page Fetch Next Result Page By Id
  • Query monitoring (2): Track Cancel Statement By Id, Track Get Statement Status By Id
  • Schema exploration (1): Browse List Database Schemas
  • Connection validation (1): Check Validate Database Connection
Connect Amazon Redshift to xpander using IAM authentication. This guide covers connecting a private Redshift cluster accessible only from the Kubernetes cluster, no public access required.
For self-hosted deployments, ensure the AWS Operator is configured with IAM role and Pod Identity before following this guide.

Prerequisites

  • A running xpander environment (cloud or self-hosted)
  • Your xpander Organization ID
  • AWS CLI access to the account

1. Create Redshift Subnet Group

Place Redshift in the same private subnets as your EKS nodes:

2. Create Security Group

Lock access to Redshift port 5439, only allow traffic from the EKS cluster security group:

3. Create Redshift Cluster

Wait for the cluster (~5-10 minutes):
Node types: dc2.large ($0.25-0.33/hr) is cheapest but not available in all regions. Use `ra3.xlplus` ($1.08-1.20/hr) as fallback. Check availability:
Get the endpoint:

4. Create IAM Role

On self-hosted, the role needs all three trust principals. On cloud, it needs only the cross-account principal: leave out the PodIdentity and SelfAssume statements below.
On self-hosted, agent-controller runs as this role through Pod Identity and calls sts:AssumeRole on the same role for each skill call, so the SelfAssume statement is required. Without it you get AccessDenied. Every assume call, this one included, passes your organization ID as the external ID. If you add an sts:ExternalId condition to SelfAssume, it must match that ID.On cloud, the assume call also passes your organization ID as the external ID. The PodIdentity and SelfAssume statements are for self-hosted.

5. Attach Permission Policies

The role needs three permission policies.

Redshift Credential Access

Redshift Data API

Self-Assume and Session Tagging

6. Create IAM-Mapped Redshift User

The username IAMR:<role-name> is a Redshift convention that maps the IAM role to a database user.

7. Associate Role with Service Account

8. Configure in xpander UI

In the xpander skill configuration, set:

9. Verify Connection

Ask your xpander agent to validate the Redshift connection. Expected result: all checks pass (path config, database, target, AWS credentials, Data API client, auth method, query execution).

Troubleshooting

Add sts:TagSession to both the trust policy AND as a permission policy on the role.
Self-hosted only. agent-controller re-assumes its own role for each skill call. The trust policy needs a SelfAssume statement for the role’s own ARN, and the role needs sts:AssumeRole as a permission policy. The call passes your organization ID as the external ID, so an sts:ExternalId condition on that statement must match it.
Add the Redshift Data API permissions policy (see step 5).
Check the Redshift security group allows port 5439 from the EKS cluster security group.
The skill path parameters (ClusterNamePath, DatabaseNamePath, CatalogNamePath) must be configured in the xpander UI with the correct values.