Now that I’m feeling comfortable with the current Fuse API for creating and running tasks on remote servers, I have revisited the SSH key management feature since a few important options were still missing.

Previously, you could add your public SSH keys so they would be authorized on newly provisioned servers. However, there was no way to add SSH keys to existing servers. Now, this is possible.

In the server list, you can edit an existing SSH key and see which servers have it authorized. You can also add the key to servers where it is not yet authorized. This is especially useful if you want to access your server from a new device that wasn’t selected during provisioning.

Another common task is to remove a key from servers where it is authorized. You can now deselect servers where the key is installed, and when you save changes, it will be deauthorized from those servers. The server selection always stays in sync.

Sometimes, you may no longer want a device to access your servers. Now, you can delete the key and it will automatically be removed from all servers where it was authorized. This is very useful.

There is one last case: you may want to remove the SSH key from your key list but keep it authorized on your servers. This is also possible. Besides deleting and removing from servers, there is an option to remove the key only from your list and keep it on the servers.

I think this fully rounds out the SSH key management feature, saving you a lot of time.