Load balancers for 10,000 or 40,000 open connections.
A load balancer takes TCP or HTTP traffic on one address and spreads it across your servers. It checks each target every 5 seconds, and its standby takes over within 10 seconds.
From €5.49 per balancer, up to 10,000 connections a month
Features
The edge of your service, run for you.
TCP, HTTP and HTTPS
Balance raw TCP, or end HTTP at the balancer and route by host name and path. The PROXY protocol passes on the client’s address.
HTTP/2 and HTTP/3
Clients connect over HTTP/1.1, HTTP/2 or HTTP/3 on QUIC. Targets receive HTTP/1.1 or HTTP/2 over the private network.
Certificates handled
Name the domains, and the balancer obtains Let’s Encrypt certificates and renews them. Or upload certificates of your own.
Health checks every 5 seconds
A TCP or HTTP check reaches each target every 5 seconds. A target leaves the rotation after 3 failed checks, and returns after 2 passes.
Targets by label
Point a balancer at a label, and servers that carry it join as they are created. Kubernetes Services do the same for nodes.
A standby built in
Every balancer runs as a pair on separate hosts. If the active one fails, the standby takes its addresses within 10 seconds.
Pricing
Two sizes, by open connections.
Each balancer includes its IPv4 and IPv6 addresses, its certificates and its standby. lb-1 holds up to 10,000 connections, and lb-2 up to 40,000.
- Load balancer, lb-1per balancer, up to 10,000 connections
- €5.49 a month, at most€0.0080 an hour
- Load balancer, lb-2per balancer, up to 40,000 connections
- €14.90 a month, at most€0.0220 an hour
Traffic through a balancer counts toward the project’s pooled allowance. Each further TB costs €1.00.
Code
A balancer in front of three servers.
lc lb creates the balancer, its listeners and its targets. The certificate is issued once DNS points at the address.
- Targets chosen by label, kept current as servers come and go.
- A redirect from HTTP to HTTPS with one flag.
- Round robin or least connections.
$ lc lb create shop-lb --plan lb-1 --region ee1 \
--network acme-net --target label=role=web \
--https shop.example.com --redirect-http
Creating shop-lb in ee1 ... active, standby ready
IPv4 203.0.113.80
IPv6 2001:db8:4c1::80
$ lc lb targets shop-lb
TARGET ADDRESS HEALTH
web-1 10.0.1.10 healthy
web-2 10.0.1.11 healthy
web-3 10.0.1.12 healthy
Questions
Questions about load balancers.
Which plan do I need, lb-1 or lb-2?
lb-1, which holds 10,000 open connections, and watch the count in the console. Move to lb-2, which holds 40,000, as the count nears the limit. The balancer keeps its addresses through the move.How does failover work?
Can a balancer reach servers in other regions?
Works with
Cloud servers
AMD EPYC vCPUs, an NVMe disk and 20 TB of traffic a month. Shared vCPUs for most work, and dedicated ones for steady load.
Kubernetes
Conformant Kubernetes with the control plane run for you and not billed. The nodes are cloud servers at server prices.
Floating IPs
Public IPv4 addresses that move from one server to another within 5 seconds. Use them for failover, or to keep an address through a rebuild.
Start with one server and one command.
Choose a region and a plan, and add an SSH key. The server answers SSH 38 seconds after the command, at the price on its spec sheet.