---
title: "Amazon Redshift Connector"
description: "Implementation notes for building and operating the Amazon Redshift connector in Tajo."
url: https://tajo.io/docs/connectors/amazon-redshift/
markdown: https://tajo.io/docs/connectors/amazon-redshift.md
lang: en-US
robots: noindex
---

# Amazon Redshift Connector

Connector status: Planned Not built yet. Tajo does not run this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Connector implementation

## Build the Amazon Redshift integration

Cloud data warehouse service for petabyte-scale analytics with SQL and BI tool integration

Data Warehouses

*Amazon Redshift connector flow from source system to Tajo mapping and Brevo activation.*

## Implementation Overview

**Build target**

Implement an Amazon Redshift connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

**Current status**

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

**Primary surface**

docs.aws.amazon.com/redshift/latest/mgmt/data-api.html

| Property | Value |
| --- | --- |
| Integration surface | Docs |
| Status | Planned |
| Category | Data Warehouses |
| Setup complexity | advanced |
| Vendor documentation | [docs.aws.amazon.com/redshift/latest/mgmt/data-api.html](https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html) |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | Not recorded |
| MCP server | Not recorded |
| Last researched | 2026-08-19 |

AWS does not publish OpenAPI for Redshift; uses AWS SDK conventions. An official AWS Labs Redshift MCP server exists but is local/stdio-only, not a hosted remote MCP, so it does not change status.

## Authentication

- Keep [docs.aws.amazon.com/redshift/latest/mgmt/data-api.html](https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html) linked from the connector runbook so operators can confirm vendor behavior during incidents.
- Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
- Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.

## Data To Sync

Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:

- Events, webhooks, and behavioral activity
- Custom objects and operational metadata

The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.

## Sync Shape

No typed contract exists for Amazon Redshift, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the [connector catalog](https://tajo.io/docs/connectors) for how contracts are promoted.

## Mapping To Tajo/Brevo

No Brevo projection is recorded for Amazon Redshift. A projection is declared on a typed connector contract, and Amazon Redshift does not have one yet, so this page will not state a mapping it cannot source.

The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the [connector catalog](https://tajo.io/docs/connectors).

## Sources

- [Vendor documentation](https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html)
- [github.com/awslabs/mcp](https://github.com/awslabs/mcp)