Support for chaining Postgres targets through SSH jump hosts in Warpgate

[vjmax]

✅ SSH Chaining Setup (Working)
I have successfully configured SSH chaining between two Warpgate instances, allowing me to connect to a private SSH target behind a jump host.

Setup:

• Outer Warpgate (publicly accessible)

• Inner Warpgate deployed

• A jump user (wg_jump) is created on the inner Warpgate and configured with the outer Warpgate’s public key.

• A private SSH target named ssh-private is added inside the inner Warpgate.

• On the outer Warpgate, I created a target:

  • Type: SSH
  • Target Name: Inner-warpgate
  • Host: ( IP of the inner Warpgate)
  • Port: 2222
  • Username: wg_jump:ssh-private

With this setup, I can successfully SSH into the private target behind the inner Warpgate by chaining through the outer Warpgate.

❌ PostgreSQL Chaining Attempt (Not Working)
Now, I would like to connect to a private PostgreSQL RDS instance (only accessible inside the inner network) using the same Warpgate chaining approach.

Steps Taken:

- Created a PostgreSQL target inside the inner Warpgate:

• Type: Postgres
• Target Name: rds-private
• Host: (Private DB host,User and Pass)
• Port: 5432

- On the outer Warpgate, I created another target:

• Type: SSH
• Target Name: Inner-warpgate-psql
• Host: (IP of the inner Warpgate)
• Port: 2222
• Username: wg_jump:rds-private

Tried accessing the PostgreSQL instance This approach does not work.

@Eugeny Is there currently any way to chain PostgreSQL targets through Warpgate, just like SSH targets or any plan for future release ?

[Eugeny]

You should be able to chain them in the same way as with SSH, though I haven't tried it - both targets should have the type set to PostgreSQL.

[vjmax]

We tried this approach, and PostgreSQL chaining is now working — thank you!