Skip to content

Operations

This page covers the security model, updates, logs, backups and support for your Sushi OpenShell instance.

Security model

  • Gateway. Listens on 127.0.0.1:17670 only, with mutual TLS. Each instance generates its own certificates on first boot; none are shared between instances or baked into the image. Host bind mounts are off.
  • Sandboxes. Workloads run as a non-root user inside Docker sandboxes, under OpenShell policies. The default policy denies outbound network access.
  • Administrators. The ubuntu user is in the docker group. Docker access is equivalent to root on the host, so everyone who can use the gateway must be a trusted administrator. This image does not isolate multiple users of the host from each other.
  • SSH. Key-only: password and keyboard-interactive login are off, and root cannot log in. The image contains no SSH keys or passwords.
  • Network. Nothing needs to be reachable from outside except, optionally, SSH. Prefer Session Manager, or limit SSH to your administrative range. The host needs outbound HTTPS for updates, container registries and any model provider you use.
  • Kernel. The image applies kernel hardening, including turning off core dumps of privileged processes.
  • Telemetry. OpenShell's upstream telemetry is turned off.

Give the instance profile only the permissions it needs, for example Systems Manager access, and never production AWS credentials. Launch with IMDSv2.

Updates

  • Operating system. Unattended security upgrades are enabled.
  • New image versions. A new Marketplace version does not update instances that are already running. To move to it, launch a new instance and move your own workloads and policies across.

Service management

The first-boot service runs once per boot and leaves the gateway running:

sudo systemctl status sushi-openshell --no-pager

The gateway runs as a user service of ubuntu, kept running after logout. As ubuntu:

systemctl --user status openshell-gateway
systemctl --user restart openshell-gateway
journalctl --user -u openshell-gateway -n 100 --no-pager

In a non-interactive session, set the runtime directory first:

export XDG_RUNTIME_DIR=/run/user/$(id -u)

Backups

Keep your own policies, provider profiles and workload files in version control or another backup you control. To back up the whole instance, take an EBS snapshot of the root volume. A snapshot includes the instance's private TLS keys and any credentials you have configured, so protect it like the instance itself.

Support

Email info@softwaresushi.com with the image version, the steps to reproduce the problem and the kind of error you see. Do not send credentials, private configuration, session keys or your own content. Guaranteed response times need a separate agreement. NVIDIA support is not included.