PuTTY and SSH

Introduction

Some EAS development activities require that the developer access an EAS Linux VM from their Windows machine to perform certain tasks, for example, to administer an EAS VM, or to perform database queries.  This page describes how to use PuTTY and Secure Shell (SSH) to access an EAS Linux VM from a Windows machine to achieve those ends.

PuTTY

Install PuTTY

Download PuTTY media from https://www.putty.org/, and install it on your Windows machine by following the instructions in the PuTTY Setup Wizard.  There is also online documentation available, for example PuTTY 0.62.

Generate Private and Public Encryption Keys

Generate Private and Public Encryption Keys

SSH

PuTTY can be used to configure and save an SSH session.  Navigate to "Chapter 2: Getting started with PuTTY" and read this short chapter before attempting to create an SSH session.

Create an SSH Login Session

Create an SSH login session if the intent is to log in to an EAS Linux (target) VM and execute Linux shell commands.  The SSH login session in this example will be for the SF DEV WEB VM (San Francisco data center, DEVelopment environment, eas WEB server, Virtual Machine).

The appropriate IP addresses will be provided by an EAS administrator for any sessions that you need to create.  Sensitive information has been redacted in the screenshots that follow.

1 Run PuTTY.

2 Under the Session category, enter the IP address of the target VM in the Host Name (or IP address) field, and specify port 2241 in the Port field.  Also confirm that the connection type is "SSH".

3 Under the Auth category and in the Private key file for authentication: field, browse to the private key file (jd_eas_private_key.ppk) that was saved in Step 5 above.

4 The remainder of the configuration consists of default values, but if additional configuration is required, then "Chapter 4: Configuring PuTTY" should be consulted.

The following login session names should be used to maintain consistency with standard EAS nomenclature.  The login session name for this example (eas-sf-dev-web) is highlighted in bold font in the table below.

5 Return to the Session category to save this login session.  Enter the login session name in the Saved Sessions field, and then press the "Save" button.

6 Before the saved login session can be tested, an EAS administrator must place your public key on the target VM.  This should already have been done in Step 7 above.

7 To test the saved login session, select the saved login session from the Saved Sessions list, press the "Load" button, and then press the "Open" button.

8 You will be prompted to log in to the target VM.  Use the username that was given to you by the EAS administrator, and when prompted a second time, enter the passphrase that was used to create your private key in Step 4 above.

9 Congratulations, you should now be logged in to the target VM!

Create an SSH Tunnel Session

Create an SSH tunnel session if the intent is to access an EAS database from pgAdmin (or another database client product) running on your Windows machine.  The SSH tunnel session in this example will be for the SF DEV DB VM (San Francisco data center, DEVelopment environment, eas DataBase server, Virtual Machine).  The appropriate IP addresses will be provided by an EAS administrator for any tunnel sessions that you need to create.  Sensitive information has been redacted in the screenshots that follow.

1 Run PuTTY.

2 Under the Session category, enter the IP address of the target VM in the Host Name (or IP address) field, and specify port number 2241 in the Port field.  Also confirm that the connection type is "SSH".

3 Under the Auth category and in the Private key file for authentication: field, browse to the private key file (jd_eas_private_key.ppk) that was saved in Step 5 above.

4 The following source port numbers should be used to prevent collisions among them on the Windows machine.  The source port number for this example (5433) is highlighted in bold font in the table below.

5 Under the Tunnels category, and in the Source port field, enter the desired source port number ("5433" in this example), and then in the Destination field, enter the desired destination port, "localhost:5432".  (The value for the destination port is the same for all of the database VMs because all of the databases are listening on port number 5432.)  Also confirm that the Local and Auto radio buttons are selected.  Press the "Add" button to add this forwarded port to the SSH tunnel session.

6 The forwarded port was added to the SSH tunnel session.

7 The following tunnel session names should be used to maintain consistency with standard EAS nomenclature.  The tunnel session name for this example (eas-sf-dev-db-tunnel) is highlighted in bold font in the table below.

8 Return to the Session category to save this tunnel session.  Enter the tunnel session name in the Saved Sessions field, and press the "Save" button.

9 Before the saved tunnel session can be tested, an EAS administrator must place your public key on the target VM.  This should already have been done in Step 7 above.

10 To test the saved tunnel session, select the saved tunnel session from the Saved Sessions list, press the "Load" button, and then press the "Open" button.

11 You will be prompted to log in to the target VM.  Use the username that was given to you by the EAS administrator, and when prompted a second time, enter the passphrase that was used to create your private key in Step 4 above.

12 Congratulations, you should now have an open tunnel from the Windows machine to the target VM!

13 Please refer to the Database page PostgreSQL SSH Tunnel Connection to learn how to use the open tunnel to connect to an EAS database.