Sh

Sozu HTTP Reverse Proxy / Load Balancer on Ubuntu 24.04 LTS

Azure Networking

A fast, memory-safe Rust HTTP reverse proxy and load balancer, reconfigurable at runtime with zero downtime.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Sozu is an open source HTTP reverse proxy and load balancer written in Rust. It is fast, memory safe, and reconfigurable at runtime with no downtime: you add or remove clusters, frontends, backends and TLS certificates on a live proxy without dropping a single connection. This cloudimg image runs Sozu 2.2.0 from the pinned upstream crate on Ubuntu 24.04 LTS as a hardened systemd service.

It suits teams who want a lightweight, memory-safe edge proxy in front of their web services, a load balancer that can be reconfigured live from the command line or a config file, or a reverse proxy whose routing policy lives in version-controllable text rather than a sprawling config.

Why the cloudimg image

The cloudimg image installs Sozu from the pinned upstream crate and runs it as the unprivileged sozu user, binding ports 80 and 443 through the CAP_NET_BIND_SERVICE Linux capability rather than as root. It is secure by default: the command and control channel is a local Unix socket only, never exposed on the network, so the proxy cannot be reconfigured remotely, and a per-VM self-signed TLS certificate is generated on first boot so no shared TLS material ships in the image. The appliance is functional out of the box, shipping a self-contained local backend and a default cluster so an on-box request returns a real HTTP body through Sozu immediately; you then point it at your own backends with one config edit and a zero-downtime reload. The paired deployment guide covers confirming the service, proving a request flows through the proxy, adding your own backends, and reconfiguring the live proxy from the CLI, and every deployment carries 24/7 support.

Common uses

  • A lightweight, memory-safe edge reverse proxy in front of your web services
  • A load balancer reconfigurable live from the CLI or a config file with zero downtime
  • A reverse proxy whose routing policy lives in version-controllable text