Skip to Content
DocumentationConnect to a Destination

Connect to a Destination

Learn how to create a warehouse destination connection from the Etleap dashboard.

Introduction

Pipelines fetch data from a Source Connection and feed into a Destination Connection. You can ingest data into five destinations with Etleap:

  1. Amazon Redshift data warehouse
  2. Snowflake data warehouse
  3. Amazon S3 Data Lake
  4. Iceberg
  5. Delta Lake

This guide uses Amazon Redshift as an example to detail the three major steps required to connect a warehouse destination with Etleap: allow inbound access, create a database user, and create the connection in the Etleap UI. The steps are similar for Snowflake.

Prerequisites

To set up a Destination Connection, you’re going to need:

  1. An existing Redshift cluster, or another support destination type: this guide uses Redshift as an example
  2. Privileges to create and modify your Redshift cluster permissions
    Note

    Perform the steps outlined here to configure your Redshift cluster to receive data pipelines.

Step 1. Create a New Destination

Once you’ve completed the prerequisites, you’re ready to create your new connection. Perform the following steps in Etleap:

  1. Select Connections from the sidebar.

  2. Click the blue +New Connection button.

  3. Select the Redshift connection type. You can use the search box to filter.

    Add a new Redshift Connection
  4. Enter a name for your connection and click Next.

Step 2. Provide Connection Parameters

Identify your Cluster’s Address

  1. Log in to AWS and go to the General information tab on your Amazon Redshift cluster’s property management page.
Note

For Redshift Serverless, the General information tab is available under the Workgroup configuration.

  1. Locate your Endpoint address.

    Hostname
  2. Copy the address, excluding the information after “.com”.

    For example:

    documentation-demo-cluster.cdxthedxl5ne.us-east-2.redshift.amazonaws.com:5499/dev

    becomes

    documentation-demo-cluster.cdxthedxl5ne.us-east-2.redshift.amazonaws.com

Enter your Connection Parameters

  1. Select your connection method (e.g., direct or SSH). Direct is the default option.

    Note

    This page assumes that you’ve already determined your connection method and implemented the required security measures to allow inbound access.

  2. Enter your cluster’s Address (e.g., hostname).

  3. Accept the default Port, or change the value to the exposed port for your cluster.

    Redshift Connection Information
  4. Paste the address into the input field and click Next.

Step 3. Provide Database Properties

  1. Enter your Username and Password.

  2. Click Next.

    Authentication step for Amazon Redshift
  3. Enter the name of your Database.

  4. Enter the Schema name (optional) and click Next.

    Amazon Redshift Database Properties

Step 4. Set Additional Properties (Optional)

You have more options to modify Redshift settings before creating the destination. These options are outlined below:

  1. Enter your User Groups if you want to grant SELECT privileges to these groups when Etleap creates tables.

  2. Select the Source only checkbox if you’d like to prohibit this database’s use as a destination.

  3. Select the Include Query Tags checkbox to add a prefix to your load queries with metadata.

  4. You can Share data with another cluster by selecting a cluster from the dropdown.

  5. Select the Enable Dynamic Varchar Widths checkbox if you want VARCHAR columns created with the minimal required width based on loaded data, automatically expanding as needed. Please note: once enabled, this option cannot be disabled.

    Redshift's additional properties
  6. Click Create Connection.

    Note

    Congratulations! You’ve now connected Etleap to your Redshift cluster.

Complete your Setup

You’re almost there! Follow the remaining steps to complete your pipeline setup:

  1. Create a source connection to extract your source data.
  2. Once that’s complete, you can create pipelines with your new source and destination connections.