13.1.1 Using ssh to Access a Server

Table of Contents Previous Next


13 Database Management : 13.1 Connecting to the Cluster : 13.1.1 Using ssh to Access a Server

EDB Ark creates an ssh key when you create a new cluster; each cluster has a unique key. Before connecting to a Postgres instance that resides on the cloud via an ssh encrypted connection, you must download the ssh key, and adjust the privileges on the key file.
C:\Users\susan\Desktop\Screen Shot 2018-12-12 at 8.40.24 AM.pngTo download your private key, navigate to the Clusters tab, and click the Download SSH Key icon. The Accessing Your Cluster Instance popup opens (see Figure 13.1).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\8910939b\Screen Shot 2018-12-12 at 8.41.11 AM.png
chmod 0600 ssh_key_file.pem
Where ssh_key_file.pem specifies the complete path and name of the EDB Ark ssh private key file.
After modifying the key file permissions, you can use ssh to connect to the cluster. Include the complete path to the key file when invoking the command provided on the Accessing Your Cluster Instance popup.
Please note: Postgres Server applications must be invoked by the Postgres cluster owner (identified when creating an EDB Ark cluster as the Master User). If you are using a PostgreSQL server, the default user name is postgres; if you are using Advanced Server, the default user name is enterprisedb. To change your identity after connecting via ssh, use the su command:
# sudo su database_user_name

13 Database Management : 13.1 Connecting to the Cluster : 13.1.1 Using ssh to Access a Server

Table of Contents Previous Next