Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.aieev.com/llms.txt

Use this file to discover all available pages before exploring further.

aircloud ssh lets you connect to a running container over SSH from your local terminal. This is the right option when you need SSH-native workflows such as:
  • scp
  • SSH tunneling
  • port forwarding with ssh -L
  • VS Code Remote SSH
Unlike Web Terminal or aircloud exec, SSH access requires image preparation and SSH key registration.

​
When to use SSH

Use aircloud ssh when you need:
  • file transfer with scp
  • SSH port forwarding
  • IDE integrations built on SSH
  • an SSH-native operational workflow

​
Register SSH keys in the console

Open the project sidebar and go to SSH Keys. Ssh Menu When adding a key:
  • enter a readable name
  • paste the full OpenSSH public key
  • choose which endpoints should receive the key
Ssh Open Key If the endpoint is already running when the key is added or changed, the new key applies from the next start or redeploy. Existing running containers keep the previous key set. Image 8

​
Important requirement

​
AirCloud-provided templates

Some AirCloud-provided templates such as Jupyter or code-oriented images can support SSH out of the box.

​
Custom images

For your own custom container image, SSH requires:
  • openssh-server installed
  • host key generation with ssh-keygen -A
  • an entrypoint that installs injected public keys into authorized_keys
  • sshd startup during container boot

​
Standard SSH setup flow

​
1. Generate a key pair locally

ssh-keygen -t ed25519 -C "your-email@example.com"

​
2. Copy your public key

cat ~/.ssh/id_ed25519.pub

​
3. Register the public key in the console

In the AirCloud console:
  1. Go to Project
  2. Open SSH Keys
  3. Add a new key
  4. Select which endpoints should receive the key

​
4. Restart the endpoint if needed

If the endpoint is already running when the key is added or changed, stop and restart it so the new environment variable injection takes effect.

​
Connect with aircloud ssh

​
Basic connection

aircloud ssh <endpoint_id>

​
Explicit identity file

aircloud ssh <endpoint_id> -i ~/.ssh/aircloud_key

​
Pin to a specific replica

aircloud ssh <endpoint_id> -r <replica_id>

​
Connect as another user

aircloud ssh <endpoint_id> -u myuser

​
Open tunnel only

aircloud ssh <endpoint_id> --tunnel-only

​
Minimal image requirements for custom containers

Your custom image should include:
  • openssh-server
  • secure SSH configuration
  • host key generation
  • startup logic for authorized_keys
  • sshd process startup

​
aircloud ssh vs aircloud exec

Itemaircloud sshaircloud exec
Requires sshdYesNo
Requires SSH key registrationYesNo
Supports scpYesNo
Supports SSH tunnelingYesNo
Supports Remote SSH toolsYesNo
Access speedSlightly slowerFaster