If your PostgreSQL instance is located in the Cloud at Amazon Web Services for example or Microsoft Azure, your preferred access to your instance will be over SSH through port 22.


In the SSH tab, first check the box 'Use SSH tunnel' to enable the rest of the form:


Reverse-engineering PostgreSQL - SSH w Private Key


Then fill in the fields:


SSH Address: IP address or DNS name of server in the cloud


Port: Tunnel port used for the SSH connection.  This defaults to 22, the standard port for SSH.


SSH User Name: Username of the profile to log into on the remote system, for which you want to establish the SSH connection.


SSH Auth method: Choice between a Private key file (typically of extension .pem) or a Password


Private key: Identity file from which the identity (private key) for SSH public key authentication is read.

On OS X using OpenSSH, identity files are found in ~/.ssh. By default, the filenames of private keys are one of the following:





On Windows, the location of identify files depends on your choice of SSH client. PuTTY is one commonly used SSH client.


Passphrase:  Used to decrypt your private keys (stored in the specified identity file), providing an extra layer of security for an SSH connection. This field is not required.


Or, if the SSH Auth Method is password:

Client key password: Used to secure the SSH connection.  This is required if you are not using an identity file.



Reverse-engineering PostgreSQL - SSH w Password