Database / BetterDB Interview questions
Explain how SSH tunnels work in BetterDB Monitor?
When you enable "Connect via SSH tunnel" on a connection, BetterDB opens an SSH connection to the bastion using either a password or a private key, then creates a local TCP tunnel and routes all Valkey traffic through it – useful for instances in a private subnet, like ElastiCache or MemoryDB.
Only a single hop is supported. The tunnel forwards to the database over 127.0.0.1 on the far side, and if TLS is enabled, the certificate is still validated against the real database hostname, not the bastion.
You can optionally pin the bastion's SSH host key fingerprint; if set, the tunnel refuses to connect unless the server presents a matching key, closing off a man-in-the-middle risk on that hop. Left blank, the server's identity isn't verified and only a warning is logged.
More Related questions...