# Singapore
ssh.singapore.render.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGVcVcsy7RXA60ZyHs/OMS5aQj4YQy7Qn2nJCXHz4zLA
```

## Usage details

### Supported key types

Render supports the following key types:

- `ed25519`
- `ecdsa`
- `rsa`

Render also supports U2F/FIDO hardware authenticated keys like a YubiKey.

- `ed25519-sk`
- `ecdsa-sk`

### Cron job connections

When you connect to a cron job from the Dashboard shell, Render spins up a new, temporary instance of the service and connects to it. This instance includes your cron job's latest build and configuration. It does _not_ automatically execute the cron job's command. After you close the shell session, Render deprovisions the instance.

It is not possible to connect to the actual cron job instances that run as part of your cron schedule.

### Automatic session closure

Render automatically closes a service's active SSH sessions in the following cases:

- The service is redeployed or restarted for any reason.
- Render is scheduled to perform maintenance on underlying infrastructure that enables SSH connections.
  - In this case, Render gives existing connections one hour before automatically closing them.

For long-running commands, consider spinning up a [one-off job](one-off-jobs) instead of SSHing into an active instance.

### Memory usage

SSH and dashboard shell sessions use the same memory pool that's allocated for your service instance. Using SSH requires about 2 MB of memory, plus about 3 MB for each active session (not including memory used by processes executed during the session).

As an example, let's say we SSH into one service instance from two different computers to run bash. In this case, memory usage would look like this:

- 8 MB for SSH
  - 2 MB for SSH access
  - 2x3 MB for the two SSH sessions
- 7 MB for bash
  - 2x3.5 MB for the two bash processes

Total memory usage in this case is about 15 MB.