Updated October 2026. The advice this post used to give was wrong, so here is the correct answer.
It previously said you could turn SSH on with the gear icon in Raspberry Pi Imager. That works for Raspberry Pi OS, but the Anthias entry in the Imager is not Raspberry Pi OS. It is a balenaOS image, and it does not read the Imager’s settings for SSH, username or wifi. Switching them on has no effect.
If you flashed the Imager entry, or a disk image from our releases
There is no SSH on these. The image is prepared to join the Anthias fleet that we run, so there is no balena dashboard of your own to open a terminal from either. That is the trade for an image that boots straight into Anthias and keeps itself updated with no command line at all.
If you want shell access
Install Anthias on top of Raspberry Pi OS Lite instead. You set the Pi up yourself, so SSH behaves exactly as it normally does and the machine stays yours:
bash <(curl -sL https://install-anthias.srly.io)
The full walkthrough is in the install guide. When you write the Raspberry Pi OS Lite card, the gear icon in the Imager does work, because that genuinely is Raspberry Pi OS. Turn on SSH there and set your username and password before writing.
If you would rather stay on balena, you can run your own fleet. Because the devices are then yours, you get balena’s own terminal and SSH.
On the original question in this thread
The reason for wanting SSH here was to add a private root CA so the viewer would trust an internal HTTPS page. On a Raspberry Pi OS install there is a script that does exactly that:
~/anthias/bin/add_certificate.sh /path/to/your-ca.crt
It installs the certificate for both the server and the viewer, including the separate store the browser engine uses, which is the part that is easy to miss when doing it by hand.