Guides

SSH access

Add keys, open a shell on a running instance, copy files, and troubleshoot connections.

Add a public key

Create a key if you do not have one

ssh-keygen -t ed25519 -a 100 -C "you@example.com"
# or keep it on a hardware key
ssh-keygen -t ed25519-sk -C "you@example.com"

Add it to your account

clockingcloud ssh-key add ~/.ssh/id_ed25519.pub --name laptop
clockingcloud ssh-key ls

Accepted types: ssh-ed25519, sk-ssh-ed25519@openssh.com, sk-ecdsa-sha2-nistp256@openssh.com, ecdsa-sha2-nistp256/384/521, and ssh-rsa of 3072 bits or more. Every key is decoded and checked on upload. Upload the .pub file only: anything that looks like a private key is rejected and never stored. Use a passphrase. The same key cannot be added twice, an account holds up to 10 keys, and you get an email with the SHA256 fingerprint (compare it with ssh-keygen -lf) whenever a key is added or removed.

You can also add keys in the console under SSH.

Connect

Terminal

clockingcloud ssh product-shots
clockingcloud ssh product-shots -- nvidia-smi
clockingcloud ssh product-shots -i ~/.ssh/id_ed25519

The instance must be running. Keys are synced to replicas when they start, so a key added after an instance started takes effect for new replicas, or after clockingcloud stop and clockingcloud start.

Copy files

Terminal

clockingcloud cp ./scripts product-shots:/workspace -r
clockingcloud cp product-shots:/out/render.png .

Remove a key

Terminal

clockingcloud ssh-key rm laptop

The key stops working for new connections immediately. Existing sessions end when their replica next syncs, within about a minute.

Something unclear or missing? Email hello@clockingcloud.com.