Data & Storage · Integration
AWS Redshift
Add AWS Redshift to your product for your customers, and give your AI agents governed access to it.
Embed an AWS Redshift integration so your customers can query their own warehouse from inside your product and read results back, with access scoped per tenant and every query logged. Schemas differ per customer, so table and column mapping is configuration rather than code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers run queries against their own warehouse from your product.
Read query results into your product without copying data elsewhere.
Read schema metadata at runtime so your product adapts to each warehouse.
Schedule refreshes so your product shows current figures.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped query to answer a question with warehouse data.
An agent reads schema metadata before composing a query.
An agent reacts to a completed refresh and updates downstream reporting.
Example prompt
Query the revenue table for the last four quarters and return the trend by region.
Set up AWS Redshift in 4 steps
- 01Open the AWS Redshift connector from your fastn dashboard.
- 02Have each customer authenticate their AWS account or cluster credentials.
- 03Map the schemas and tables your product queries.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the AWS Redshift integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS Redshift integration without building it. Your customers connect their own AWS Redshift account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AWS Redshift update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS Redshift connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
AWS Athena
Snowflake
BigQueryOften used alongside
Tools the same teams tend to run next to AWS Redshift, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceAWS Redshift integration FAQ
How do I add an AWS Redshift integration to my product?
Enable the AWS Redshift connector in your fastn dashboard, then let each customer authenticate their own AWS Redshift account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS Redshift client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own AWS Redshift account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS Redshift account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this AWS Redshift integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped query to answer a question with warehouse data.
Who maintains the AWS Redshift integration?
fastn does. When AWS Redshift changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the AWS Redshift integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large AWS Redshift reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the AWS Redshift integration?
A common starting point: run queries against their own warehouse from your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the AWS Redshift integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS Redshift does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS Redshift to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.