Easegress on Ubuntu 24.04 LTS

Azure Application Infrastructure

Easegress, an open source cloud native traffic orchestration system that routes, load balances and secures HTTP traffic through declarative pipelines.

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

Easegress is a free, open source traffic orchestration system for HTTP services. It sits in front of your applications as a programmable gateway, matching incoming requests against declarative routing rules and passing each one through a pipeline of composable filters that can proxy to backend pools, load balance across them, validate credentials, rewrite headers, apply rate limiting and circuit breaking, and mirror or mock traffic. Configuration is declarative and applied at runtime with the egctl command line client against a REST administration API, so routes and policies change without restarts or redeployments, and the whole gateway runs as a single binary with an embedded configuration store rather than a cluster of moving parts. It suits teams that want an API gateway, reverse proxy and traffic management layer they can define as configuration and version alongside their services.

Why the cloudimg image

cloudimg delivers Easegress fully installed under systemd with a working gateway you can send traffic through the moment the instance boots: a health probe, a demonstration route that is genuinely proxied and round robin load balanced across two backends, and an authenticated administration route. The image is secure by default. The administration API and its embedded configuration store are bound to loopback only, so nothing administrative is reachable from the network, and the one administration path that is exposed is gated by a credential generated uniquely on each machine's first boot, so no secret is ever shared between instances. The gateway runs as an unprivileged system user, the egctl client is on the path for immediate use, and every deployment carries a paired deployment guide and 24/7 support.

Common uses

  • Front your services with an API gateway and reverse proxy
  • Load balance and route HTTP traffic with declarative pipelines
  • Apply authentication, rate limiting and resilience at the edge