Connecting with ssh

Connecting with SSH

To connect with ssh, specify the complete path and name of your SSH private key in the connection string. You should always use the identity of the pgedge user when connecting to the External IP Address noted in the pgEdge Cloud console. Use the following signature when connecting:

ssh -i path_to_key_file/key_file_name.pem pgedge@external_IP_address

To locate the External IP Address, select the name of the cluster in the pgEdge Cloud console tree control. Scroll down to the Nodes tab, and select the name/location of the node to which you wish to connect. The first IP address in the Node Information section is the address you should use for SSH connections.

Configure Cloud Environment

Managing SSH Keys for Clusters Provisioned on AWS

When you define a pgEdge Cloud cluster provisioned by AWS, you are given the option to specify the name of an SSH key pair; provide a key pair name if you plan to connect via SSH.

The same key must exist in each region in which a node is provisioned. For example, if your cluster will have nodes in Virginia, Oregon, and Frankfurt, your key pair must also exist in Virginia, Oregon, and Frankfurt in the AWS management console.

The easiest way to distribute a key across multiple regions is to create the key on your localhost with the ssh-keygen command, and then import the public key into each cloud provider region using the AWS console. To review the Linux man page for the ssh-keygen command, visit here (opens in a new tab); if your localhost is a Windows system, visit here (opens in a new tab).

Managing SSH Keys for Clusters Provisioned on Azure

If you are provisioning a cluster on Azure, reach out to pgEdge support (opens in a new tab) for the key pair associated with your cluster.

Managing SSH Keys for Clusters Provisioned on Google

If you are provisioning a cluster on Google, you can use the Google console to associate an SSH key with the cluster after the cluster is created. The steps are:

  1. Link your Google Account with the pgEdge console.
  2. Create a provisioned cluster.
  3. Edit the instance definition in the Google Cloud console, adding the SSH key to the VM definition.

To identify the pgEdge cluster in the Google console, you should look for nodes that have matching cluster IDs in the regions in which you provisioned the pgEdge cluster. After locating each node, edit the node configuration, using the + ADD ITEM option in the Security and access settings to add your SSH keys to the project.

Add SSH Key on Google console