> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/reference/data-sources/redshift.md).
# AWS Redshift
## **Configuration**
### Prerequisites
If your database is hosted behind a Firewall, you need to add our [IP addresses](/concepts/data-sources.md#whitelisting-ip-addresses) to the Firewall whitelist.
### Connecting the data source
To connect your Redshift database, follow the steps below:
1. On the **Data sources** page, click **Connect**, and select *AWS Redshift* in the Data sources list.
2. Specify all the required credentials and test the connection.
3. If successful, proceed to connecting the data source to complete the setup.
If you need to be able to override the default data source database with a custom value in the action, you can enable the **Allow override database name in action** setting in the *Data source connection* window**.** \
Once enabled, you will be able to specify a custom database when configuring an action. In case a database is not specified, the default data source database will be used.
## Usage
Once you have established the connection between UI Bakery and your Redshift database, you can start interacting with its data.
To manage data from AWS Redshift, you can use the [SQL Query](/reference/working-with-actions/sql-query.md) action step.
{% hint style="danger" %}
Note that pre-defined actions, such as *Load Table*, *Create Row*, etc. are NOT supported with this datasource.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uibakery.io/reference/data-sources/redshift.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
