​

Before you connect

• CONNECT on the database
• USAGE on the target schema(s)
• SELECT on the tables you want to expose

​

Connection fields

​

SSH Tunnel fields

​

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.

​

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.

​

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.

​

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.

​

SSL

• 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

• 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

• 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;

​

Troubleshooting