This guide will walk you through how to create, edit, and remove a destination that you can use to transfer data into Redshift.
Before you begin
Before you create a Redshift destination, please make sure all prerequisites have been met. Learn more about the prerequisites for creating a Redshift destination.
The configuration stage of creating a new destination for Redshift in the Supermetrics Team Site includes the following fields.
- Display name is the destination’s display name. Display names distinguish different destinations from each other.
- Hostname is the server name of the Redshift cluster you’re going to use as a destination. You can obtain this from the AWS console by navigating to Clusters → General information → Endpoint.
If there’s additional information for Port and Database attached to the Endpoint link you can copy, please delete everything after “amazonaws.com” before filling in the hostname.
For example, cluster-name.random-value.region.redshift.amazonaws.com:5439/demo_db should be shortened to cluster-name.random-value.region.redshift.amazonaws.com.
- Database name is the name of the database in Redshift. You don’t need to use the cluster database here — this can be a Redshift database.
- Database schema is the name of the destination database schema. Redshift provides a default schema called “public” that you can use instead of creating your own, if you need.
Note: A Redshift database schema is not equivalent to a schema you select when creating the transfer, or a custom schema that you can create in the Supermetrics Query Manager.
- Username is your Redshift cluster admin username.
- Password is your Redshift cluster admin password. When editing an existing destination, this field will be “New password”, and inputting anything to the field will overwrite the last password used.
If you don’t have the password for this user, please contact your AWS administrator.