Reach a Private Database Safely
To build models from a database that isn't openly reachable — one in a VPC or private subnet, or behind a firewall — FunnelStory needs a network path to it. There are two mechanisms; this guide helps you pick and set up the right one, safely.
1. Pick the mechanism
- Reachable but firewalled (a public endpoint that restricts traffic by IP) → allowlist FunnelStory's egress IPs.
- Fully private (no public endpoint — VPC/private subnet) → SSH tunnel through a bastion host.
2. Allowlist FunnelStory's egress IPs
Add FunnelStory's static egress addresses to your firewall or security group (and to any IP-restricted bucket or endpoint policy). The current addresses are on Allowed IP addresses — link to that page rather than copying the IPs, since they can change.
3. Or set up an SSH tunnel
For a fully private database, set up a tunnel through a bastion/jump host:
- Go to Configuration → Tunnels and add a tunnel with the bastion host, port, and SSH key.
- Point the database connection at the private host through the tunnel.
See SSH tunnels for the full setup.
4. Use a read-only user
Whichever path you choose, connect with a least-privilege, read-only database user scoped to the schemas and tables you'll model. FunnelStory only reads.
5. Connect and build the model
With the path open, add the database connection (for example PostgreSQL) and build your Account model on it.
Related
- Allowed IP addresses — FunnelStory's static egress IPs.
- SSH tunnels — reach a database in a private network.
- Data connections overview