Skip to main content
Amazon Redshift data warehouse makes it simple and cost-effective to efficiently analyze all your data using your existing business intelligence tools. For more on how to use Amazon Redshift, see: Amazon Redshift documentation. You can create a direct connection to your Amazon Redshift account that allows you to easily export Crisp’s source and normalized data tables.

​
Requirements

To create this connection you will need to meet the following requirements: For provisioned clusters:

​
Setting up the connection in Crisp

  1. Log into your Crisp account.
  2. From the main menu on the left side of the screen, select ****Connectors.
main_menu_connectors.png
  1. Select the Add connector button.
connector_setup_add.png
  1. Select the Data Destinations tab, then select the Amazon Redshift connector tile.
  2. You will need your Amazon Redshift account ID to setup the connection. If you need to get your account ID, log in to Amazon Redshift, then select your account name (e.g., Crisp ) at the top right corner. A menu appears with your account ID at the top. You can select the copy button to the right of the ID to copy it.
Amazon_Redshift_001.png 6. If you want, update the default name of the connector, then enter or paste your Amazon Redshift account ID _.\ Amazon_Redshift_005.png _ 7. Select the cloud region, e.g., US East (Ohio), used for the Amazon Redshift account. If you need to look up the cloud region used for your account, you can log in to Amazon Redshift and see the cloud region at the top-right corner of the screen.\ Amazon_Redshift_006.png Note : Crisp currently only supports two cloud regions: US-East-2 (Ohio) and US-West-2 (Oregon), but may expand access to additional regions in the future.
  1. In the _Connector source data _section, select the **Select **button.
    Amazon_Redshift_007.png
    The Select source data screen appears.
  2. Select the retailer(s) for which you want to export data (e.g., UNFI ), then choose which data tables and columns to include in the export. For detailed instructions on making your data feed selections, see Selecting Destination Data Sources.
Hint: You can select the book icon to the right of a table name to see its documentation.
  1. To complete your selections, select the Accept button.
Excel_Outbound_004.png
The window closes and you return to the connector setup screen.
  1. Choose additional columns to include in your export:
  • If you want to include a column that identifies which source connector the data came from, select the Include Source Connector Configuration ID option.
    Hint : This is useful if you have multiple connectors for the same retailer, such as one for U.S. sales and one for Canadian sales.
  • If you want to add a column that provides the date and time data was last sent from Crisp to the destination, select Include Last Exported Timestamp.
    Note : Crisp retroactively ingests and re-exports data for a set period of time after the initial data capture, known as a lookback period, to account for changes from the source (such as missing register sales added later). You can use the last exported timestamp column to confirm if data was recently exported from Crisp to help troubleshoot issues or reduce costs by automating how often data flows from a destination to other systems at your organization. For more on retroactive data changes, see Data changes for destination connections.
  1. Select the Save button.
connector_setup_save.png The connection setup is complete. You can check the status of the connection by clicking the new Amazon Redshift tile.

​
Accessing Crisp Data in Amazon Redshift

Once you create the Amazon Redshift connection in Crisp, to access your data, you need to associate the datashare that was automatically created during the connection process to your entire AWS account or specific cluster namespaces in your account. The name of datashares created via Crisp connection begin with crisp_data. For instructions on how to associate your Crisp datashare, see: Amazon Redshift Documentation > Associating datashares. Note : If you have issues associating the datashare, please review the Requirements at the beginning of this article.

​