PUMA setup to enable submission of suites to ARCHER

Following the ARCHER change to 2-factor authentication we have had to alter the way we connect to ARCHER to allow submission of Rose/Cylc suites.

Currently this route is only configured for ARCHER login node7 (, but will be rolled out to all login nodes very soon. Once rolled out to all the login nodes, the temporary master socket solution will no longer work.

Step 1

  • Generate an id_rsa_archerum ssh-key if you haven't already. This will only be used for submitting jobs to ARCHER.
    ssh-keygen -t rsa -b 4096 -C "" -f ~/.ssh/id_rsa_archerum

Use a good and not-blank passphrase that you haven’t used before.

Note: It is essential the key is named id_rsa_archerum. We shall collect the public key and forward it to ARCHER.

  • NCAS-CMS will let you know when your key has been installed on ARCHER.

Step 2

  • In your PUMA ~/.ssh/config file add the following section:
      User <archer_username>
      IdentityFile ~/.ssh/id_rsa_archerum
      ForwardX11 no
      ForwardX11Trusted no
  • Add your id_rsa_archerum key to your ssh-agent by running: ssh-add ~/.ssh/id_rsa_archerum
  • Specify as the host in the appropriate .rc file (suite.rc or site/archer.rc). For example; host =
  • Submit your suites as usual

Note: You will not be able to login interactively via Once all login nodes have been updated, it will no longer be possible to login to ARCHER interactively from PUMA. You will have to login from your local desktop or institution.

If you have any problems please contact the CMS Helpdesk.

Last modified 15 months ago Last modified on 30/07/20 13:07:25