Setup
The settings referenced in this article (except IP whitelist, which is entirely controlled on your end) go on https://app.faraday.io/destinations. You'll need to "Create destination" and give your Redshift instance a descriptive name first.
IP whitelist
Please make sure our IP addresses are allowed by your cluster or load balancer's security group.
User
Please set up a user for us:
create user faraday_receive password 'xxx'It is called faraday_receive because you will receive data from it. If you also add your Redshift as a Source in Faraday, that will use a different user.
By default, this user will have access to your public schema, including the ability to list existing tables and create new tables, but won't be able to read any existing tables. That's correct as far as we are concerned.
If you want to limit our ability to list existing tables (remember: we can't read their contents, only write to them), or if you want us to create tables in a new schema, please let us know.
Table
Please tell us what table name we should use. For example, you might want us to put scores/personas/etc into a table called faraday_data.
We assume that you want us to operate in the public schema. If you have a custom schema name, please let us know.
Database URL
Please provide a URL for us to connect to.
The Redshift console has a convenient helper for this:
Load balancer
If your Redshift cluster is on a private IP, you may have set up an AWS Elastic Load Balancer in front of it.
In that case, we also need the public load balancer hostname. Here are some examples:
clientname-data-public-elb-xxxxx.us-east-1.elb.amazonaws.comredshift.clientname.comThe reason we need this information is that your Redshift cluster will terminate the SSL connection using its private hostname (*.redshift.amazonaws.com) but we will be connecting to its load balancer hostname (*.elb.amazonaws.com) and we need to explicitly allow this discrepancy.
(Optional) Schema
Most clients have us write to a single table inside of their public schema. But some clients use a different schema internally, or they want us to only have access to a Faraday-specific schema.
In that case, the user setup may be more complicated - please let us know so we can support you.