Skip to main content

PostgreSQL

Instructions for syncing data into Vitally via PostgreSQL

Written by Laura Bedoya
Updated over a week ago

Requirements

  1. Your PostgreSQL instance must allow inbound traffic from our Authorized Static IP Addresses. You can maintain a 'Deny All' firewall policy and only grant access to our specific IPs to ensure the connection remains private and secure.

  2. Create unique PostgreSQL credentials, using password authentication for Vitally's access to the database and grant the user permission to the required tables.

  3. Safe-list Vitally's Authorized IP addresses in any relevant security groups:

    • For US-hosted Vitally customers: 52.2.105.119, 34.198.95.164, 54.225.45.200, 3.233.54.92, 44.197.82.135, 44.205.137.47, 3.231.135.245, 34.234.2.125, 18.117.45.34, 18.118.174.158, 3.128.104.4, 3.128.39.40, 3.137.39.224, 3.20.73.62

    • For EU-hosted Vitally customers: 13.50.117.250, 13.48.176.93, 13.48.142.17, 13.53.227.107, 16.171.90.148, 16.170.120.57, 16.171.215.121, 16.171.156.82

Step 1 - Connect

We'll need these values to connect to your Postgres warehouse:

  • Host: The public hostname of your Postgres warehouse.

  • Port: The port number of your Postgres warehouse. By default, it is 5432.

  • Database: The name of the database that you want to connect to (e.g. production).

  • Username: A unique user that you've created for Vitally.

  • Password: That user's password.

Step 2 - Configure Sync

Step 3 - Enable Sync

FAQ

What permissions does the user connection PostgreSQL need?
The PostgreSQL user requires read credentials.

Did this answer your question?