Accessing an Arvados VM with SSH - Windows Environments

This document is for accessing an Arvados VM using SSH keys in Windows environments. If you would like to use to access VM through your browser, please visit the Accessing an Arvados VM with Webshell page. If you are using a Unix environment (Linux, OS X, Cygwin), please visit the Accessing an Arvados VM with SSH – Unix Environments page.

Arvados requires a public SSH key in order to securely log in to an Arvados VM instance, or to access an Arvados Git repository. The three sections below help you get started:

Getting your SSH key
Adding your key to Arvados Workbench
Using SSH to log into an Arvados VM instance

Getting your SSH key

(Note: if you are using the SSH client that comes with Cygwin, please use instructions found in the Accessing an Arvados VM with SSH – Unix Environments page.)

We will be using PuTTY to connect to Arvados. PuTTY is a free (MIT-licensed) Win32 Telnet and SSH client. PuTTY includes all the tools a Windows user needs to create private keys and make SSH connections to your virtual machines in the Arvados Cloud.

You can download PuTTY from its Web site. Note that you should download the installer or .zip file with all of the PuTTY tools (PuTTYtel is not required).

If you downloaded the zip file, extract it to the location you wish to install the PuTTY applications. This document assumes that you installed PuTTY in the default directory under C:\Program Files\ or C:\Program Files (x86)\ (if you are using a 64 bit operating system).

Step 1 – Adding PuTTY to the PATH

After downloading PuTTY and installing it, you should have a PuTTY folder in C:\Program Files\ or C:\Program Files (x86)\ (if you are using a 64 bit operating system).
Open the Control Panel.
Select Advanced System Settings, and choose Environment Variables.
If you are using newer systems like Windows 10, you may use the following to open Advanced System Settings. Open Control Panel. Click on System and Security. Click on System. Click on Advanced system settings and choose Environment Variables…
Under system variables, find and edit PATH.
If you installed PuTTY in C:\Program Files\PuTTY\, add the following to the end of PATH:
;C:\Program Files\PuTTY
If you installed PuTTY in C:\Program Files (x86)\PuTTY\, add the following to the end of PATH:
;C:\Program Files (x86)\PuTTY
Click through the OKs to close all the dialogs you’ve opened.

Step 2 – Creating a Public Key

Start PuTTYgen from the Start Menu or the folder where it was installed.
At the bottom of the window, make sure the ‘Number of bits in a generated key’ field is set to 4096.
Click Generate and follow the instructions to generate a key.
Click the Save public key button.
Click the Save private key button (we recommend using a strong passphrase).
Select the text of the Public Key and copy it to the clipboard.

Step 3 – Set up Pageant

Pageant is a PuTTY utility that manages your private keys so is not necessary to enter your private key passphrase every time you make a new SSH connection.

Start Pageant from the Start Menu or the folder where it was installed.
Pageant will now be running in the system tray. Click the Pageant icon to configure.
Choose Add Key and add the private key which you created in the previous step.

You may now proceed to adding your key to the Arvados Workbench.

Adding your key to Arvados Workbench

From the Workbench dashboard

In the Workbench top navigation menu, click on the dropdown menu icon to access the user settings menu and click on the menu item SSH keys to go to the SSH keys page. Click on the + Add new SSH key button in this page. This will open a popup as shown in this screenshot:

Paste your public key into the text area labeled Public Key, and click on the Submit button. You are now ready to log into an Arvados VM.

To see a list of virtual machines that you have access to and determine the name and login information, click on the dropdown menu icon in the upper right corner of the top navigation menu to access the user settings menu and click on the menu item Virtual machines to go to the Virtual machines page. This page lists the virtual machines you can access. The Host name column lists the name of each available VM. The Login name column will have a list of comma separated values of the form you. In this guide the hostname will be shell and the login will be you. Replace these with your hostname and login name as appropriate.

Initial configuration

Open PuTTY from the Start Menu.
On the Session screen set the Host Name (or IP address) to “shell”, which is the hostname listed in the Virtual Machines page.
On the Session screen set the Port to “22”.
On the Connection → Data screen set the Auto-login username to the username listed in the Login name column on the Arvados Workbench Virtual machines_ page.
On the Connection → Proxy screen set the Proxy Type to “Local”.
On the Connection → Proxy screen in the “Telnet command, or local proxy command” box enter:
plink -P 2222 turnout@switchyard.pirca.arvadosapi.com %host
Make sure there is no newline at the end of the text entry.
Return to the Session screen. In the Saved Sessions box, enter a name for this configuration and click Save.

Note: We recommend you do not delete the “Default” Saved Session.

Connecting to the VM

Open PuTTY from the Start Menu.
Click on the Saved Session name you created in the previous section.
Click Load to load those saved session settings.
Click Open to open the SSH window at the command prompt. You will now be logged into your virtual machine.

Note: If you see a hung PuTTY terminal window with no further action: open a new Command Prompt window using the Windows → Start menu and type plink -P 2222 turnout@switchyard.pirca.arvadosapi.com shell in it. Please make sure to replace shell with the hostname listed in the Virtual Machines page. Hit enter and type y when prompted to cache the session state. Go back and start PuTTY session using the start menu button.

You should now be able to log into the Arvados VM and check your environment.

Previous: Accessing an Arvados VM with SSH - Unix Environments Next: Checking your environment