Faraday’s can tap right into your AWS Redshift to share data to your Faraday account.

Doing so, we can utilize your lead, customer, and churn data for predictive outcomes, e.g. "Lead generation, lead conversion, or likelihood to churn, or simply append Faraday data back into your Redshift, or other destinations!

Granting access

Redshift user creation docs: https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_USER.html

1: Create a “read-only” user for Faraday in your Redshift 

2: Whitelist the following IP addresses, so our services can connect

34.233.255.242

52.204.223.208

52.204.228.32

52.204.230.227

52.22.91.248

52.23.137.21

54.174.177.114

3: All the information we need can be formatted in a JDBC URL , a url that contains the information we need to login. A JDBC url  looks like this:

redshift://faraday1:FakePassword@cluster-redshiftcluster-h2e1y2e978had.cxmkjxwwbofc.us-east-1.redshift.amazonaws.com:5439/customer_database

4. If you use a load balancer (also called an ELB ), we need the load balancer URL AND the full Redshift URL. This comprises around 30% of Redshift integrations. 

Example ELB URLs:

clientname-data-public-elb-xxxxx.us-east-1.elb.amazonaws.com 

redshift.clientname.co

Example Full Redshift URLs:

cluster-redshiftcluster-h2e1y2e978had.cxmkjxwwbofc.us-east-1.redshift.amazonaws.com 

cb-us-east-1-prod-financewarehouse.sam232yad2ha6.us-east-1.redshift.amazonaws.com

5. Please see https://knowledgebase.faraday.io/en/articles/2887608-what-fields-are-required-when-sending-data-to-faraday for the information we need. If you already know what schema and tables you want to grant us access to, please do so, otherwise, your Customer success manager will schedule a data discovery call with you and a Faraday Customer success engineer to determine what data we will need access to.

6. Create a new Source on https://app.faraday.io/sources, select Redshift as a Source type, and add properties for the JDBC URL and ELB

Did this answer your question?