Load balancers

A load balancer runs inside the tenant’s VPC and spreads requests over healthy targets. It terminates TLS, matches listener rules (host, path, method, header, source address, query) and applies middleware.

Part	What it is
Load balancer	The endpoint. internet-facing gets a floating IP and a name, lb-<id>.elb.<region>.<parent>; internal gets a private address only.
Listener	A port and protocol (HTTP, HTTPS or TCP), forwarding to a target group by default.
Rule	A condition on a listener that overrides the default forward.
Target group	The backends: instances, NICs or IP addresses, health-checked. Only healthy targets get traffic.
Certificate	A certificate and key for HTTPS listeners, selected by SNI.

stratumctl lb load-balancers create web --type application --scheme internet-facing \
  --vpc-id vpc-abc123 --subnet-ids subnet-abc123 --project p-web
stratumctl lb target-groups create web-tg --vpc-id vpc-abc123 --port 8080 \
  --protocol http --target-type instance --project p-web
stratumctl lb targets register tg-abc123 --target-id i-abc123 --port 8080 --project p-web
stratumctl lb listeners create lb-abc123 --port 80 --protocol HTTP --target-group tg-abc123 --project p-web

HTTPS:

stratumctl lb ssl-certificates upload web-cert --cert-file web.pem --key-file web.key --project p-web
stratumctl lb listeners create lb-abc123 --port 443 --protocol HTTPS --target-group tg-abc123 --project p-web
stratumctl lb ssl-certificates attach lis-abc123 --certificate cert-abc123 --project p-web

The load balancer is active once the platform has placed it. Reach it by its floating IP, or by name once the LAN forwards the parent domain (LAN access). Its security groups and the targets’ groups must allow the traffic.

The console’s API and admin tools are served by the platform’s own load balancer, the front door, at stratum.<parent>.