Private databases
Configure an SSH jump host or run RDST inside the database network.
An SSH jump host lets RDST reach a database in a private network. RDST opens a local tunnel through the host and uses it for the database connection.
Configuring a jump host
- Open the target in Settings, or select Add target and open Manual setup.
- Enter the database's private endpoint, port, and database name. Use the address the jump host can reach.
- Expand Connect via SSH jump host.
- Choose a saved host or Enter manually.
- Enter the jump host address, SSH port, user, and private-key path.
- Select Test connection to test the tunnel and database together.

RDST reads the private key to authenticate. It doesn't copy the key. The target list shows Tunnel active while the tunnel is open.
Reusing a jump host
Select the same saved jump host for each database it can reach. Editing that host updates the targets that use it.
If one database fails while another works through the same host, check routing and security rules between the host and the failing database.
Monitoring through a tunnel
RDST Agent needs the SSH host and database to remain reachable. RDST manages the tunnel while it collects readings. If the connection fails, check the Inbox and the connection details.
AWS discovery imports endpoints; you still need to configure the route to a private database.
Other network paths
For VPN access, connect the VPN first. RDST uses your computer's routing.
If the database is reachable only inside its network, install the
CLI on a host there. Run
rdst web and
forward its local port over SSH. Keep rdst web running to collect monitoring
history.