Stitch only supports Postgres versions 8.2 and above. While this isn't something that's strictly enforced, we recommend keeping your version current as a best practice.
Click here for more info on replicating your views.
In this article, we'll walk you through connecting your PostgreSQL database to Stitch via an SSH Tunnel. You'll need some tech expertise to complete the setup, so we recommend looping in a developer or a member of your tech team to help out if you haven't done this before.
Connecting a PostgreSQL database is a seven-step process:
The Public Key is used to authorize the Stitch Linux user. In the next step, we'll create the user and import the key.
To retrieve the key:
Leave this page open throughout the tutorial - you'll need it in the next section and at the end.
For the connection to be successful, you must configure your firewall to allow access from our IP addresses. Whitelist the following IPs before continuing onto the next step:
sshd_config file associated with the server is not set to the default option, only certain users will have server access - this will prevent a successful connection to Stitch. In these cases, it's necessary to run a command like
AllowUsers to allow the Stitch user access to the server.
This can be a production or slave machine, as long as it contains real-time (or frequently updated) data. You may restrict this user any way you like as long as it retains the right to connect to the PostgreSQL server.
Note that anything inside square brackets -
[like this] - is something you need to define when running the commands yourself.
To create the new user, run the following commands as
root on your Linux server:
adduser [stitch username] -p mkdir /home/[stitch username] mkdir /home/[stitch username]/.ssh
To ensure the user has access to the database, we need to import the Public Key from the first step into
authorized_keys. Copy the entire key into the
authorized_keys file as follows:
touch /home/[stitch username]/.ssh/authorized_keys "< [PASTE KEY HERE] >" >> /home/[stitch username]/.ssh/authorized_keys
To finish creating the user, alter the permissions on the
/home/[stitch username] directory to allow access via SSH:
chown -R [stitch username]:[stitch username] /home/[stitch username] chmod -R 700 /home/[stitch username]/.ssh
In the next step, you'll create a database user for Stitch.
Your organization may require a different process, but the simplest way to create this user is to execute the following query when logged into Postgres as a user with the right to grant privileges. This user should also own the schema that Stitch is being granted access to.
CREATE USER [stitch username] WITH ENCRYPTED PASSWORD '[secure password]';
GRANT CONNECT ON DATABASE [database name] TO [stitch username];
GRANT USAGE ON SCHEMA [schema name] TO [stitch username];
GRANT SELECT ON ALL TABLES IN SCHEMA [schema name] TO [stitch username];
ALTER DEFAULT PRIVILEGES IN SCHEMA [schema name] GRANT SELECT ON TABLES TO [stitch username];
[secure password] with a secure password, which can be different than the SSH password. Additionally, make sure you replace
[database name] and
[schema name] with the appropriate names in your database.
If you want to connect multiple databases or schemas, repeat this process as necessary.
To wrap things up, we need to enter the connection and user info into Stitch. Did you leave the PostgreSQL credentials page open? If not, click the Add an Integration button on the dashboard and then click the PostgreSQL icon. Don't forget to select the SSH Tunnel option from the Encryption Type menu.
postgres_marketingin the data warehouse.
In addition, click the Connect using SSL checkbox if you're using an SSL connection.
The Replication Frequency controls how often Stitch will attempt to replicate data from your data warehouse. By default, the frequency is set to 30 minutes, but you can change it to better suit your needs.
When you're finished, click the Save Integration button to complete the setup.
Now that your PostgreSQL database is connected to Stitch, the next step is selecting the tables and fields you want to sync.