Using DBeaver’s Built‑in SSH Tunnel for JDBC Connections to Private Databases
Configure DBeaver’s SSH tunnel to reach private databases through a bastion host, including key authentication, permission checks, and verification steps.
Loading…
ReadMeFeed / Community knowledge
#bastion-host
Real questions. Useful conversations. Find the people who know your stack.
dbeaverReplacing Bastion Hosts with IAP TCP Forwarding for Secure VM Access
Replace bastion hosts with Google Cloud IAP TCP forwarding to give administrators SSH/RDP access to VMs without public IPs. IAM controls access, Cloud Audit Logs provide a trail, and no extra instances to patch.
googleDBeaver SSH Tunneling: Connecting to Databases Behind a Bastion Host
DBeaver's SSH tunnel routes database traffic through a bastion host without a VPN. Learn the correct connection settings, verification steps, and common configuration mistakes.
Securing Database Access with DBeaver SSH Tunneling
Stop exposing your database ports to the public internet. Learn how to use DBeaver's built-in SSH tunneling to securely access private databases via a bastion host.
Shared Tmux Operations Sessions on a Bastion Host: An Architecture Note
A single tmux server on a bastion host with a dedicated UNIX socket gives multiple operators a persistent, shared shell. This note covers the minimal design, trust boundaries, and failure modes.
tmuxSSH Agent Forwarding: When Convenience Meets Risk
SSH agent forwarding lets a bastion host use your local private key without copying it, but any process on that host can also request signatures. This post shows a concrete bastion‑to‑target flow, the security trade‑offs, and a practical mitigation checklist.
sshPuTTY Local Port Forwarding: Reaching a Database Through a Bastion Host
How to configure PuTTY's local port forwarding through the Tunnels panel to reach an internal database via a bastion host — plus the plink equivalent, verification steps, and the security trade-offs.
puttyBuilt-in SSH tunnel vs OS-level port forwarding for bastion access without persisting production credentials
Goal is to test an integration to a remote database behind a bastion host without exposing production ports and without storing production credentials in DBeaver connection settings. Testing should use non-production credentials only. DBeaver offers a built-in SSH tunnel configured in the connection editor that is created and closed with the database connect