Skip to main content
Connect Supaboard to a PostgreSQL database for direct querying, schema discovery, and AI-powered analysis.

​
Before you connect

Network access — Supaboard connects from a fixed set of egress IPs. Add them to your database firewall allow-list before attempting a connection. The current IP list is shown inside the connector form under Whitelist IPs. Database user permissions — The user you provide needs at minimum:
  • CONNECT on the database
  • USAGE on the target schema(s)
  • SELECT on the tables you want to expose
See Recommended database user permissions for the exact SQL.

​
Connection fields

FieldDefaultRequiredDescription
Display Name—YesLabel shown in the Supaboard UI
Host—YesHostname or IP of your PostgreSQL server
Port5432YesPostgreSQL port
DatabasepostgresNoDatabase name; Supaboard auto-discovers if left blank
Username—YesDatabase user
Password—YesPassword for the database user
SchemapublicNoDefault schema for queries
Additional JDBC Parameters—NoExtra key=value pairs appended to the JDBC URL

​
SSH Tunnel fields

Shown when the SSH Tunnel toggle is enabled.
FieldDefaultRequiredDescription
SSH Host—YesHostname or IP of the SSH bastion server
SSH Port22YesSSH port on the bastion server
SSH Username—YesSSH login username
SSH Connection TypePrivate KeyYesPrivate Key or Password
SSH Private Key—If Private KeyPEM-encoded private key
SSH Passphrase—NoPassphrase for an encrypted private key
SSH Password—If PasswordPassword for SSH password authentication

​
Finding your connection details

​
Amazon RDS for PostgreSQL

  1. Open the RDS Console and select your instance.
  2. Under Connectivity & security, copy the Endpoint — this is your Host.
  3. The default Port is 5432.
  4. Your Database name was set when the instance was created (visible in the Configuration tab).
  5. Ensure the RDS security group allows inbound TCP on port 5432 from Supaboard’s egress IPs, or use an SSH tunnel.
Documentation: Connecting to a PostgreSQL DB instance · RDS for PostgreSQL overview

​
Amazon Aurora (PostgreSQL-compatible)

  1. In the RDS Console, open your Aurora cluster.
  2. Use the Writer endpoint as your Host for read/write access; use a Reader endpoint for read-only.
  3. Port is 5432 by default.
  4. Add Supaboard IPs to the cluster’s VPC security group.
Documentation: Connecting to an Aurora PostgreSQL cluster · Aurora PostgreSQL overview

​
Google Cloud SQL for PostgreSQL

  1. Open the Cloud SQL Console and select your instance.
  2. Under Connect to this instance, copy the Public IP address as your Host.
  3. Under Connections → Authorized networks, add each Supaboard egress IP.
  4. Alternatively, use the Cloud SQL Auth Proxy via an SSH tunnel.
Documentation: Cloud SQL for PostgreSQL overview · Connecting overview · Authorizing with IP addresses

​
Azure Database for PostgreSQL

  1. Open your server in the Azure Portal.
  2. On the Overview page, copy Server name — this is your Host (format: server.postgres.database.azure.com).
  3. Under Settings → Connection security, add a firewall rule for each Supaboard egress IP.
  4. SSL enforcement is enabled by default on Azure — enable the SSL toggle in Supaboard.
Documentation: Azure Database for PostgreSQL documentation · Firewall rules

​
SSL

Enable the SSL toggle when your database requires encrypted connections (recommended for all cloud-hosted instances).
  • SSL Certificate — paste the server’s CA certificate in PEM format if your database uses a self-signed or private CA certificate. Leave blank for certificates signed by a public CA.

​
SSH Tunnel

An SSH tunnel routes the database connection through a bastion host, keeping your database off the public internet entirely. When to use it:
  • Your database has no public IP
  • You want to avoid adding Supaboard IPs to your database firewall
  • Your security policy requires all external connections to go through a jump server
Checklist:
  • The bastion server can reach the database host on port 5432
  • Supaboard’s egress IPs are allowed on the bastion server’s SSH port (default 22)
  • The SSH user has permission to forward connections (no no-port-forwarding in authorized_keys)
  • If using a private key, it is in PEM format (OpenSSH format may need conversion with ssh-keygen -p -m PEM)

​
Recommended database user permissions

-- Create a dedicated read-only user
CREATE USER supaboard WITH PASSWORD 'strong_password_here';

-- Allow connection to the database
GRANT CONNECT ON DATABASE your_database TO supaboard;

-- Allow schema access
GRANT USAGE ON SCHEMA public TO supaboard;

-- Allow reading all current tables
GRANT SELECT ON ALL TABLES IN SCHEMA public TO supaboard;

-- Allow reading future tables automatically
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT ON TABLES TO supaboard;
Replace public with each schema you want to expose. Run the GRANT USAGE and GRANT SELECT blocks for each schema.

​
Troubleshooting

ErrorLikely causeFix
Connection refusedWrong host or port, or firewall blockingVerify host/port; add Supaboard IPs to firewall allow-list
password authentication failedWrong username or passwordDouble-check credentials; confirm the user exists in this database
database "X" does not existDatabase name typoCheck database name in your RDS/Cloud SQL console
SSL connection requiredServer requires SSL but toggle is offEnable the SSL toggle
FATAL: no pg_hba.conf entryDatabase server not configured to accept connections from this IPAdd Supaboard egress IPs to pg_hba.conf or use an SSH tunnel
could not connect to server: Connection timed outBastion/SSH host unreachableVerify SSH host, port, and that Supaboard IPs are whitelisted on the bastion
Last modified on March 11, 2026