Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
bordertrue
titleThis page:

Table of Contents
maxLevel1

You have now created a Nimbus instance. The last steps involve logging in to the instance via SSH log in, which is described below, and attaching a storage volume for storing data and running your analyses from. Later, you may also want to transfer data from your local computer, if required.

Login via Terminal


On Linux and macOS, you can log in to Nimbus by opening a shell on your computer's default terminal.

What you need

  • The private key pair file that was created in the Nimbus dashboard for your instance.
    1. It is best practice to save the private key pair file to the ~/.ssh location in your local host.
    2. If you have not done so, run the following commands if you downloaded the private key pair to your "Downloads" folder, you can use these commands:

      Code Block
      mv ~/Downloads/My_Key_Pair.pem ~/.ssh/My_Key_Pair.pem
      chmod 600 ~/.ssh/My_Key_Pair.pem ##this creates the right permissions for the private keypair

      Sometimes there may be folder ownership permissions preventing you from moving files into it. You can check the ownership of the ~/.ssh folder by doing:

          ls -lh ~/.ssh 

If you don't see your computer username in the third column, this would be why.  You can use sudo to move the file on your computer if necessary:

          sudo mv tick.pem ~/.ssh/tick.pem

If you cannot move it to that folder, you will just need to ensure you save your SSH keys in a folder that you will not lose/forget, as you will need that for logging in to the instance


  • The login_name, which is the Linux OS image you chose:

    Ubuntuubuntu
    Centos
    Rocky Linuxrocky
    CentOS Streamec2-user
    CentOScentos
    Fedorafedora
    Scientific Linuxroot
    Debiandebian


  • The public external IP attached to your Nimbus instance, e.g. ###.###.##.##

SSH Login on the terminal

Code Block
ssh –i-i ~/.ssh/My_Key_Pair.pem login_name@###.###.##.##


Log in via Visual Studio Code


Visual Studio Code is a free and open source code editing software that can be deployed on Linux, macOS and Windows. It has an integrated terminal within its user interface that removes the need to switch between command-line tasks and code editing. The default terminal shell is bash on Linux and macOS, and PowerShell on Windows. *For Windows users to configure the default terminal shell to bash, an installation of Git from https://git-scm.com/downloads is required before installation of Visual Studio Code.

You can download Visual Studio Code from the following link: https://code.visualstudio.com.

To log in to Nimbus, follow the instructions as per above.

Recommended settings in Visual Studio Code

Although the integrated terminal on visual studio code can be used directly to SSH log in to Pawsey systems, a useful feature of Visual Studio Code is the Remote Development extension pack that is easily installed from the Marketplace within the application. It allows the ability to open remote directories and text files on Visual Studio Code for in-app code editing and building.

Once installed, connect to Pawsey systems as follows:

  1. Click on the green button in the bottom left corner of the screen and select the first option Remote-SSH: Connect to Host...
  2. Select + Add New SSH Host...

  3. Log in using your Nimbus key pair and external IP address, e.g. ssh -i ~/.ssh/My_Key_Pair.pem ubuntu@###.###.##.## (Note: if using a Windows path, e.g. C:\Users\Username\.ssh\My_Key_Pair.pem, you will need to use double slashes, i.e. C:\\Users\Username\\.ssh\\My_Key_Pair.pem)
  4. Save the host details in the default config file, e.g. /Users/yourcomputername/.ssh/config
  5. Once the host details is saved, click Connect. A prompt appears for you to enter your Pawsey password.


  6.  Review the new window with the integrated terminal that opens. In the bottom left corner, you can see that you are connected to the remote host.


Note: To use code editing interactively, use the command code to open and edit text files from your remote directories, e.g. typing the command code sample.txt will open the <sample.txt> file within Visual Studio Code.

To troubleshoot any issues, visit https://code.visualstudio.com/docs/remote/troubleshooting

Login via Windows with PuTTY


What you need

  • Your instance’s IP address -> get this from the instance overview in your dashboard ###.###.###.###

  • Your login_name -> this depends on the name of the Linux OS image you selected

    Login names:

    | Ubuntu | ubuntu |

    | Debian | debian |

    | Fedora/Centos/Scientific Linux | fedora/centos/root |

  • The location and name of your private key pair, for eg "MyKeyPair.ppk". If you have not yet generated your Putty private key, follow these steps:

  1. Open PuTTYgen (All Apps -> Putty -> Puttygen)
  2. Click the LOAD button.
  3. Select the .pem file you downloaded from the Nimbus dashboard. If you cannot see your .pem file , select All Files instead of Putty Private Key Files from the drop-down bottom menu.
  4. Set a new passphrase and confirm it for your private key.
  5. Click the Save private key button and give it the name you prefer.

Steps to log in

  1. Open Putty.
  2. Under Host name (or IP address), type: login_name@###.###.###.###
  3. In the menu on the left, expand SSH and click on Auth.
  4. Under the section Authentication parameters, click on Browse....
  5. Select your previously create .ppk private key.
  6. Click on Open to start the connection to your instance.

Login via Windows with MobaXTerm


To install MobaXTerm: 

  1. Go to the download for MobaXTerm Home Edition: http://mobaxterm.mobatek.net/download-home-edition.html.
    1. If you do not have Admin rights, select the Portable Edition
    2. If you have Admin rights, select either the Installer Edition (or the Portable Edition). 

      Note: The Portable version is an executable file that you choose where to save it and launch it. For example, you can save it to a folder on your computer, on a USB drive or any other media. The Installer version puts MobaXTerm into a specific folder (usually Program Files), creates shortcuts to it, and includes an uninstaller.

      IMPORTANT: If you receive an error on the MobaXTerm download, click the arrow and click Resume. The file is large and download times may vary/timeout. 
  2. Select the version to install.
  3. Extract the zipped file.
  4. Go to the extracted file (exe file) and double-click it. This action launches the MobaXTerm window. 

  5. To set preferences for your MobaXTerm session: 
    1. Click Settings in the top tool bar. 
    2. From the drop-down menu, select Configuration. The MobaXTerm Configuration window displays. 
    3. On the General tab, confirm all defaults remain as illustrated here: 
  6. To set SSH setting, click the SSH tab: 
    1. In the SSH-browser setting section, unclick the Enable graphical SSH-browser checkbox.  You uncheck (turn this off) so you do not create unnecessary connections to the remote host. 
    2. In the SSH settings section, confirm X11-Forwarding is enabled (checked). 
  7. Click OK to save the changes. The MobaXTerm home page displays

To launch a MobaXTerm session:

On the MobaXTerm home page, click the Start local terminal button or click Enter. A new tab displays with the MobaXTerm window ready for use.


Login via Windows with Windows Terminal / PowerShell / cmd


To install Windows Terminal:

  1. Windows PowerShell, Command Prompt, and Terminal offer similar functionality and all can be used to SSH into your Nimbus instance.  Windows Terminal is the newest application and is an open-source project that supports Bash (Bourne Again Shell).  It now comes standard with Windows 11 but can be installed via Microsoft Store : https://apps.microsoft.com/store/detail/windows-terminal/9N0DX20HK701
  2. Change permissions of the .pem file you downloaded (from https://pawseysc.github.io/using-nimbus/05-access-and-use-instance/index.html)

    On Windows, SSH will work regardless of whether the key file is only readable by you. To modify the key’s permissions, locate it in Windows Explorer, right-click on it then select Properties. Navigate to the Security tab and click Advanced.

    Image Added

    Disable inheritance and remove all permissions.
    Image Added

    Then add a new permissions entry.
    Image Added

    Click Select a principal and enter your user name. The easiest way to do this seems to be to enter the email address associated with your Microsoft account (the one listed under your profile information on the computer you are using), and then press Check Names. Otherwise, you can select the advanced option and it reveals a more comprehensive search engine for you to use.
    Image Added Image Added



    Clear all permissions then grant yourself Full Control and apply the changes.
    Image Added

    Your key file should now have security settings that look like those shown below.
    Image Added


SSH via Terminal / PowerShell / cmd:

  1. Open up your preferred command-line client and enter the following (if in the folder of the downloaded .pem file) 


    ssh -i 'name_of_your_key'.pem 'login_name'@###.###.###.###

    For further details visit https://pawseysc.github.io/using-nimbus/05-access-and-use-instance/index.html

Image Added

Image Added


Panel
titleAlso in this section:

Child pages (Children Display)
pageAccess and Use Your Nimbus Instance