Redshift Serverless


Faraday easily integrates with AWS Redshift, enabling you to embed AI-powered predictive analytics anywhere else in your stack. Discover your brand's bespoke personas, score your customers for churn risk, find repeat purchasers, and more, enabling you to confidently engage the right customers, at the right time, with personalized, relevant content. The best part? No code—and no PhD—required.

Getting started

Make sure you have a Faraday account (signup is free!) and that it's not in test mode.


You'll need the following details to create your connection to Redshift Serverless:

  • Host required
  • AWS Region required — Redshift tables exists inside of an AWS region, e.g. us-east-1
  • Schema required
  • Port required
  • Load balancer DNS name optional — In case the host is deployed behind a load balancer.
  • User required
  • SSH bastion optional — In case the host is deployed behind an SSH bastion / jump server. Uses the Faraday SSH public key. This is the address of the bastion including username. For example,
  • Password required
  • Database required


Setting up your connection

First, you'll need to grant Faraday access to Redshift Serverless.

Amazon Redshift Serverless is the next generation version of Amazon Redshift that doesn't require you to pick a cluster size in advance.

Amazon Redshift is a data warehouse. It is wire-compatible with Postgres and so connections are host-based and require a user and password. We suggest that you create a Faraday-only schema to both send and receive data. Within this schema, Faraday would have full read and write access. Alternatively, you can give Faraday access to certain tables in a shared schema.

This connection type can be placed behind an SSH bastion (aka jump server). In that case, specify the user and host of the SSH bastion.

This connection type can also be placed behind a load balancer. In that case, specify the host of the load balancer. Faraday suggests that you use an unguessable string somewhere in the path to your data. This avoids what is called the Confused deputy problem

For example, instead of naming an S3 bucket s3://faraday-acme/, name it s3://faraday-acme-pwiiprz162ez. This guarantees that malicious actors cannot guess the name and request that Faraday import data from it into their account. The same logic applies to any path that is used to locate data.

Creating your connection

Now you can connect Faraday to Redshift Serverless.

  • In the navigation sidebar, choose Connections. Screenshot of the empty connections list
  • Click the New Connection button.
  • Fill out the form
    • Choose Redshift Serverless.
    • Skip "Step 1" — you've already completed it!
    • For "Step 2," fill out the connection details you gathered above.
    • Enter a memorable name, like "My Redshift Serverless connection". Screenshot of the new connection form, filled out
    • Click the Save connection button.

Screenshot of the connections list with the correct connections showing
Wait briefly while Faraday establishes your connection. It shouldn't take long.

Your new connection is now ready to use!