Faraday easily integrates with Google Cloud SQL, 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.
You'll need the following details to create your connection to Google Cloud SQL (SQL Server):
- Instance connection name required — For use with Cloud SQL proxy. Client must enable Cloud SQL Admin API and give IAM role "Cloud SQL Client" to our service account firstname.lastname@example.org (Datasets) or email@example.com (Targets).
- Load balancer DNS name optional — In case the host is deployed behind a load balancer.
- 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, firstname.lastname@example.org
- User required
- Password required
- Database required
First, you'll need to grant Faraday access to Google Cloud SQL (SQL Server).
Google Cloud SQL is a hosted database service. Connectivity is shared with a GCP IAM user while database access is shared with a user and password.
Which IAM account (or both) depends on use of Targets and/or Datasets:
- Give service account Cloud SQL client permission on Project Microsoft SQL Server connections are host-based and require a user and password. We suggest that you create a Faraday-only database to both send and receive data. Within this database, Faraday would have full read and write access. Alternatively, you can give Faraday access to certain tables in a shared database.
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-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
Now you can connect Faraday to Google Cloud SQL (SQL Server).
- In the navigation sidebar, choose Connections.
- Click the New Connection button.
- Fill out the form
Your new connection is now ready to use!