SSH tunnels & VPC peering
Connect databases that have no public endpoint.
If your database lives in a private network with no public endpoint, Queringo can still reach it over an SSH tunnel or through VPC peering. This keeps the database closed to the internet while letting Queringo connect.
SSH tunnel
A bastion (jump) host with a public address forwards Queringo's connection to the private database.
- Provision a bastion host
Stand up an SSH bastion that can reach the database on its private address.
- Add Queringo's key
Authorize Queringo's tunnel public key on the bastion so it can open the forward.
- Configure the tunnel in the connector
In the connection form, enable the SSH tunnel and enter the bastion host, port, and user. Queringo connects to the database through it.
VPC peering
For higher-throughput or fully private setups, peer Queringo's network with yours so the database is reachable on a private route without a bastion. This is typically arranged on enterprise plans.
Either way, the database stays closed to the public internet. Restrict access so only the bastion or peered route can reach it.
Troubleshooting
- Tunnel connects but the database does not: confirm the bastion can reach the database's private host and port.
- Authentication failed on the bastion: check that Queringo's tunnel key is authorized and the SSH user is correct.
What's next
Back to Connect a data source, or see Managing sources.