Requesting an Account

Account Request Process

The MIT Supercloud is intended to support research collaboration between MIT LIncoln Laboratory and students, faculty and researchers at MIT and other academic institutions.  Once an account request is made it requires approval prior to creation.  If you are working on a project that can benefit from supercomputing resources please send a request to supercloud@mit.edu with the following information:

  • Name
  • Affiliation
  • Name of research collaborators
  • Reason for creating account: e.g., research project, online course
  • Operating system on machine you will use when connecting to supercomputer
  • High Performance Computing experience level
  • For researchers:
    • Brief description of project needs, e.g., high performance databases, software, accelerators (GPUs)
    • Any shared groups that you need to be added to
  • ssh keys for the machine you will access your account from, see below for instructions on setting up your keys

Generating ssh Keys for Supercloud Authentication

If you have any issues or questions regarding the generation of ssh keys, please contact the team at supercloud@mit.edu. To access the system you will need passwordless ssh keys, be sure that you do not use a password/passphrase when generating your keys.

Windows:

For Windows we recommend using PuTTY as an ssh client.  PuTTY is a free, open source ssh client for Windows systems. To access the system you will need passwordless ssh keys, be sure that you do not use a password/passphrase when generating your keys.

  • Instructions for installing PuTTY are here. (Please note, the link will open in a new window.)
  • Once PuTTY is installed please follow the instructions at this link to manually generate your ssh-keys.  (Please note, the link will open in a new window. Only follow the instructions in the "Generating an SSH Key" section. We will put it in place once you send it to us.)
  • Once you have generated your ssh keys, please send us the id_rsa.pub file

 

MacOS and Linux:

If you have no existing ssh keys, from the command line in a terminal window, follow the steps below.  If you already have ssh keys that do not use a password then you can use those. Note these keys must be password/passphrase-less.  Please send us the public key, id_rsa.pub

[user1234@yourMachine]$ ssh-keygen -t rsa

You will see the following:
Generating public/private rsa key pair.

When answering the 3 requests (1st 3 lines) just hit return to create passwordless keys and save them in the default location.

Enter file in which to save the key (/home/user1234/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/user1234/.ssh/id_rsa.
Your public key has been saved in /home/user1234/.ssh/id_rsa.pub.
The key fingerprint is:
88:90:6a:dc:f1:bd:ed:fb:b1:aa:46:14:34:5e:b9:70 user1234@yourMachine
The key's randomart image is:
+--[ RSA 2048]----+
|      .o ..      |
|   .  .ooE       |
|  o.   .+ .      |
|....o..o .       |
|.o ...o.S        |
|.      .o        |
|      .. . .     |
|       ..   o    |
|      ...++o     |
+—————------------+
To view your public ssh key, go to your .ssh directory
[user1234@yourMachine]$ cd .ssh

* In ~/.ssh you would see two files id_rsa and id_rsa.pub .  We want the content of the id_rsa.pub file sent to us or the entire file itself.

[user1234@yourMachine]$ ls

id_rsa  id_rsa.pub

[auser1234@yourMachine]$

*This is the id_rsa.pub file content after generating a public SSH key that we would require. To view it, type cat id_rsa.pub at the command line.

[user1234@yourMachine]$ cat id_rsa.pub 

ssh-rsaAAAAB3NzaC1yc2EAAAABIwAAAQEA1NAD8v4nFzQ6G7KIEzkDLOnlH7t/4zmw0vVXlJjjFW4kLBgLJa0tkk61jHCxO2CurDr4zdEs2NeHG9agZJgMKMJZdIVaxtPcEBVVaNutvn/ZDRe3VsrRjToKEoR0xlAUdoef++AwiwI6K6vBOGIq6whLIlY5L9tZJfaLF3xMwmQRRhf4C+al/yZ5hX7BfGba2fqZmugTPpeSbLnFMVPKK/wy6XZasBSAKgLBA141EMXIKuGrpXpxLMECPBN5GDd/xmjmD0pC2o2z5OdfdYJj/FRWL2sC8hWTZSPa4p/n7Qc9ErFW5wM7FkynwguN4t/A+QOCa+p8C/nrOcTQKugrtw==user1234@yourMachine

*This file content would be added to the user’s ~/.ssh/authorized_keys file from each machine that they intend on connecting to TX-E1 from.