This page shows how to add, use and remove SSH keys, API keys and registry credentials. You manage all three on the console's Credentials page.
| Credential | What it's for |
|---|---|
| SSH key | Connecting to instances with SSH. |
| API key | Using the CLI. |
| Registry credentials | Pulling private container images. |
SSH keys let you connect to running instances with your own SSH client. Each key belongs to you, and every instance in your organization accepts the keys of all its members.
~/.ssh/id_ed25519.pub, and click Add key.featherless-cloud ssh-keys add
featherless-cloud ssh-keys add ~/.ssh/work.pub --name work-laptop
API keys let the CLI and your scripts act as you. You can create and revoke them only in the console.
| Scope | Read | Write |
|---|---|---|
| Instances | View instances, Run Jobs, logs, metrics and network volumes. | Also create, change and delete them, and open terminals. |
| Account | View your profile, templates, SSH keys and registry credentials. | Also change them. |
Write includes read. Give each script or person its own key with the narrowest scopes it needs, so you can revoke one without affecting the others.
A key acts in the organization that was active when you created it. To use another organization, switch to it in the console and create a key there.
Open the key's actions menu, click Revoke key, and confirm. Anything using the key stops working immediately.
Keys belonging to instances with the CLI installed are hidden unless you switch on Show instance keys. They end when their instance stops. See Use the CLI in an instance.
Registry credentials let instances and Run Jobs pull private container images. They belong to the organization, and only owners and admins can add, change or remove them.
ghcr.io), a Username, and a Password or access token.echo "$GHCR_TOKEN" | featherless-cloud registry-keys add ghcr --server ghcr.io --username my-user --password-stdin
Use an access token with read-only pull access where your registry supports it. When you deploy, Automatic picks a matching credential for the image's registry, or you can choose one. See Custom images.
A credential that running instances use can't be deleted, and its registry can't be changed.