Reference · built on requestConnectorDatabases & warehouses

Amazon Redshift

Warehouse tables and query results from Amazon Redshift, over JDBC and ODBC drivers or the asynchronous Data API over HTTPS.

Request accessPricing ↗

About

Amazon Redshift is the data warehouse from Amazon Web Services, offered as Redshift Serverless workgroups or provisioned clusters, and it is based on PostgreSQL with a columnar engine built for analytic queries. Clients connect with the Amazon Redshift JDBC, ODBC, or Python drivers at jdbc:redshift://endpoint:port/database; the Redshift team does not test or support PostgreSQL drivers. The Redshift Data API runs SQL over an HTTPS endpoint with no persistent connection: ExecuteStatement returns an id, DescribeStatement reports progress, and GetStatementResult pages the rows. Credentials come from AWS Secrets Manager or from temporary database credentials tied to an IAM identity.

An operator on Fibric runs the queries you approve against the schemas you grant and proposes row changes for review, each with a receipt and an undo.

This is a reference listing. It documents what Fibric would read from Amazon Redshift and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from tables and views the database user may SELECT, over JDBC, ODBC, or the Python connector
  • Asynchronous query results from the Data API through ExecuteStatement, DescribeStatement, and GetStatementResult, in JSON or CSV
  • Schema, table, and column metadata from ListSchemas, ListTables, and DescribeTable
  • Statement history and status from ListStatements, including the SessionId used for session reuse
  • External data in Amazon S3 through Redshift Spectrum external tables, when you define them

Proposed actions

  • Target capability: propose an INSERT or UPDATE against a named table, submitted once with a ClientToken so a retry does not repeat it
  • Target capability: propose a BatchExecuteStatement that runs several statements as one transaction and rolls back if any fails

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reconcile a board figure against warehouse rows

    Run the governing query through the Data API, page the result with GetStatementResult, and show the reviewer which rows moved the number since the last read.

    With Metric Reconciliation, KPI Drift

  • Know when a load stopped landing

    Query the newest load timestamp per table each morning and raise a notice when a feed misses its expected window.

    With Data Freshness, Morning Brief

  • Keep an eye on warehouse workloads

    Read statement history from ListStatements and flag a scheduled workload whose runtime grows past its usual span.

    With Cost Anomaly, Idle Resources

Requirements

  • A Redshift Serverless workgroup or a provisioned cluster in a VPC, with a database and the schemas to read
  • An IAM role permitted to call the Data API and the GetClusterCredentials or GetCredentials operation
  • For driver connections, network reach to the endpoint on the port set when the cluster was created (5439 in the documented example)
  • For Secrets Manager authentication, a secret holding username and password for the database
Authentication
Temporary database credentials from GetClusterCredentials, GetClusterCredentialsWithIAM, or redshift-serverless:GetCredentials for an IAM identity, or a username and password stored in AWS Secrets Manager.

Limits

  • A Data API query may run for at most 24 hours, its statement is at most 200 KB, and results are kept for 24 hours
  • A Data API result larger than 500 MB after gzip compression ends the call
  • Each Data API operation has a transactions-per-second quota, such as 30 for ExecuteStatement and 20 for GetStatementResult, before throttling
  • Some PostgreSQL features, such as secondary indexes and efficient single-row data manipulation, are omitted

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Amazon Redshift ↗

Questions and answers

Do I need a persistent database connection?
Not with the Data API. It is an HTTPS endpoint: ExecuteStatement submits SQL and returns immediately, DescribeStatement reports status, and GetStatementResult or GetStatementResultV2 fetches JSON or CSV pages. Driver connections over JDBC or ODBC still need network reach to the endpoint.
Can I use a PostgreSQL driver?
Amazon Redshift is based on PostgreSQL and AWS previously recommended the PostgreSQL JDBC and psqlODBC drivers, but it now states those are not tested or supported by the Redshift team. Use the Amazon Redshift JDBC, ODBC, or Python drivers, which add IAM and federated sign-in.
How does IAM sign in to the database?
The driver or the Data API calls GetClusterCredentials, or GetClusterCredentialsWithIAM for a user derived from the IAM identity such as IAM:foo, and connects with the temporary credentials returned. Serverless workgroups use redshift-serverless:GetCredentials.
Ask about Amazon Redshift

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Amazon Redshift through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy