Embiro BI

Documentation › Connecting data

Firewalls and SSH tunnels

Reach a database behind a firewall - allow Embiro BI's fixed IP address 13.49.213.196, or connect through an SSH jump host.

Most company databases are protected by a firewall that only lets known addresses in. Embiro BI always connects from the same fixed IP address, so you can allow it precisely. If your database is on a private network, connect through an SSH jump host instead.

Option 1: allow Embiro BI's IP address

Every connection Embiro BI makes comes from:

13.49.213.196

The Connect database dialog shows the same address under Database behind a firewall?

Allow that address on your database's port, 5432 for PostgreSQL or 3306 for MySQL. Where you do this depends on where the database runs:

Amazon RDS or Aurora
EC2 console → Security groups → the database's group → Edit inbound rules → add a rule: type PostgreSQL (or MySQL/Aurora), source Custom 13.49.213.196/32. The database must also have Public access set to Yes.
Azure Database
The server's Networking page → Firewall rules → add 13.49.213.196 as both start and end IP.
Google Cloud SQL
The instance's Connections → Networking → Authorized networks → add 13.49.213.196/32.
Supabase
Supabase allows all addresses by default. If you turned on network restrictions, add 13.49.213.196/32 under Database settings → Network restrictions. Use the Session pooler host and the username postgres.<project-ref>.
Your own server

Allow the address in the server's firewall, for example sudo ufw allow from 13.49.213.196 to any port 5432. For PostgreSQL, also add a line to pg_hba.conf:

text hostssl sales embiro_reader 13.49.213.196/32 scram-sha-256

and make sure listen_addresses in postgresql.conf includes the public interface.

Only private addresses?

Embiro BI refuses to connect to private and internal addresses, such as localhost, 127.0.0.1, 10.x.x.x, 172.16-31.x.x and 192.168.x.x. It runs in the cloud and can't reach your office network directly. Use an SSH tunnel (below) or give the database a public address.

Option 2: connect through an SSH jump host

An SSH tunnel goes through a server you control (a jump host or bastion) that is reachable from the internet and can itself reach the database. The database can stay on a private address.

You need:

  • a jump host with a public address and SSH open to 13.49.213.196;
  • an SSH account on it, with a password or, better, a private key;
  • the jump host's SSH host key, so Embiro BI can check it is talking to your server.

Get the jump host's host key

On any computer that can reach the jump host, run:

ssh-keyscan -t ed25519 bastion.example.co.ug

It prints one line such as:

bastion.example.co.ug ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB4o...

Copy the whole line. Embiro BI refuses to connect if the jump host's key doesn't match, which protects your database password from a server pretending to be yours.

Set up the tunnel

  1. In Connect database, fill in the database details as seen from the jump host. For example Host 10.0.1.25 (the database's private address) and Port 5432.
  2. Switch on SSH Tunnel.
  3. Fill in:
    • SSH Host: the jump host's public name or IP, such as bastion.example.co.ug;
    • SSH Port: usually 22;
    • Username: the SSH account;
    • Login with: Password, or Private Key (paste the whole key, including the -----BEGIN and -----END lines) with its Private Key Password if it has one;
    • SSH Host Key: the line from ssh-keyscan.
  4. Click Connect.

SSH tunnels are a plan feature ("Database connection via SSH tunnels"). If your plan doesn't include it, the switch explains how to add it. See Plans and features.

Checking it works

Connect tests the connection before saving. If it fails:

  • timeout: the firewall is still blocking 13.49.213.196, or the host or port is wrong;
  • password authentication failed: check the username and password (for Supabase, the postgres.<project-ref> username);
  • no pg_hba.conf entry: add the pg_hba.conf line above and reload PostgreSQL;
  • host key mismatch: run ssh-keyscan again and paste the new line.

More in Common problems.

Something unclear or missing? Tell us and we'll improve this page.