Feature Request: Add SSH bastion (jump host) support #429

New Issue

MrUnknownDE · 2026-04-05T16:16:27+02:00

MrUnknownDE commented

2026-04-05 16:16:27 +02:00

Originally created by @allen0099 on 11/7/2025

Currently, the software provides direct connection options for PostgreSQL instances, but it lacks a mechanism to connect through an SSH bastion (jump host). In many environments, especially in secured VPCs or on-premise networks, database instances are only accessible via a bastion host for security reasons.

Requested feature:

Add support for connecting to PostgreSQL databases via an SSH tunnel or bastion host.
- Allow configuration of SSH host, username, key, and port.
- Optionally support ProxyCommand or agent-based authentication.

Additional question:
Could you please clarify the current level of support for AWS Aurora (PostgreSQL-compatible) databases?

Are all backup features fully functional with Aurora?
Are there any known limitations or differences compared to standard PostgreSQL instances?

Use case example:
In a private AWS environment, the Aurora cluster is only reachable through an EC2 bastion host. Direct database connections are not permitted for security compliance reasons. Having SSH tunneling support would enable backups in such restricted environments without exposing the database to public networks.

*Originally created by @allen0099 on 11/7/2025* Currently, the software provides direct connection options for PostgreSQL instances, but it lacks a mechanism to connect through an SSH bastion (jump host). In many environments, especially in secured VPCs or on-premise networks, database instances are only accessible via a bastion host for security reasons. **Requested feature:** * Add support for connecting to PostgreSQL databases via an SSH tunnel or bastion host. * Allow configuration of SSH host, username, key, and port. * Optionally support ProxyCommand or agent-based authentication. **Additional question:** Could you please clarify the current level of support for **AWS Aurora (PostgreSQL-compatible)** databases? * Are all backup features fully functional with Aurora? * Are there any known limitations or differences compared to standard PostgreSQL instances? **Use case example:** In a private AWS environment, the Aurora cluster is only reachable through an EC2 bastion host. Direct database connections are not permitted for security compliance reasons. Having SSH tunneling support would enable backups in such restricted environments without exposing the database to public networks.

MrUnknownDE closed this issue

2026-04-05 16:16:27 +02:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/databasus#429