BFE on Ubuntu 24.04 LTS

Azure Networking

BFE is an open source layer 7 load balancer and reverse proxy, routing traffic to the right backend by host, path, header or cookie.

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

BFE, originally Baidu Front End, is an open source layer 7 load balancer and reverse proxy, and a Cloud Native Computing Foundation sandbox project. It terminates client traffic and forwards it to the right backend using content based routing: requests are matched on host, path, header, cookie, query string or client address, then balanced across named clusters and sub clusters with health checking and configurable retries. It speaks HTTP, HTTPS, HTTP2, WebSocket, gRPC and FastCGI, carries a modular plugin framework for rewriting, redirecting, blocking, tagging and rate limiting traffic, and exposes rich built in counters so operators can see exactly what the edge is doing.

Why the cloudimg image

cloudimg delivers BFE fully patched and already proxying on first boot: a bundled local demo backend gives the load balancer something real to route to, so the appliance proves itself standalone with nothing else to deploy, and a shipped self test command confirms a genuine request travelled through BFE and came back with the backend's response. The metrics endpoint and the demo backend are restricted to the loopback interface, and every published key the upstream release ships, four private keys, a session ticket key, a signing key and two seeded accounts, is stripped out; the TLS certificate and session ticket key are generated per instance at first boot, so no key material ships in the image. Paired deployment guide and 24/7 support.

Common uses

  • Front a fleet of application servers with content based routing and health checked failover
  • Terminate TLS at the edge and split traffic by host or path across separate backend clusters
  • Run a programmable layer 7 gateway with rewrite, redirect, blocking and traffic tagging rules