Load Balancers
A load balancer is a single public address that spreads incoming traffic across several of your servers. Clients connect to the load balancer, and it forwards each request or connection to one of your servers (its backends). If a backend stops answering its health check, the load balancer stops sending it traffic until it recovers.
Think of it as a receptionist: visitors always come to the same front desk, and the desk sends each one to a colleague who is free.
When to use a load balancer
If you have only one server, you don’t need a load balancer yet. Point your domain at the server’s Reserved IP instead.
How it works
- You create the load balancer and list your backends (an IP address or hostname plus a port for each). IBEE gives it a public hostname, such as
3f9c2b7e-….lb.ibee.ai, and a listener port. - Clients connect to that hostname and port. You can point your own domain at it with a DNS record.
- The load balancer checks each backend on a schedule (a health check) and picks a healthy one for each request or connection, using the routing algorithm and backend weights.
- The backend answers through the load balancer. Your backend sees the connection coming from the load balancer, not from the client.
Layers and protocols
A load balancer works at one of two layers. Layer 7 (L7) understands web requests (HTTP), so it can route by URL path or header. Layer 4 (L4) only sees network connections (TCP) and forwards them without reading them. You choose the layer and protocol when you create the load balancer, and you can’t change them later.
TLS (Transport Layer Security) is the encryption behind https://. See SSL and TLS termination for how each mode handles certificates.
You don’t pick a location for a load balancer. It runs on IBEE’s shared load-balancing service and reaches your backends at the addresses you give it.
What a load balancer can do
Three options on the create form are saved with the load balancer but not applied to traffic yet: Sticky sessions, Proxy protocol, and Encrypt traffic from the load balancer to this backend. Don’t rely on them. Traffic from the load balancer to your backends is unencrypted, and your backends don’t receive the client’s address through proxy protocol.
Before you begin
- A verified organization. Until identity verification is complete, the portal shows Verify Identity instead of Create Load Balancer. See Verify your identity.
- At least one backend that the load balancer can reach. For a VM, that is its public IPv4 address. The load balancer is not inside your VPCs, so it can’t reach VPC-only private addresses. See Attach VMs.
- A firewall rule that lets traffic reach the backend port, for both requests and health checks. See Create firewall rules.
- For the API: an API token with Load Balancer permission (
load-balancer.readto view,load-balancer.writeto create, change or delete) and your workspace ID.
To create one now, follow Create a load balancer.
Limits
Billing
Billing starts when the load balancer becomes active and stops when you delete it. IBEE’s price list for load balancers has these items:
- each hour the load balancer is active;
- HTTP requests (L7);
- data processed, in and out;
- new connections and connection time (L4).
The charges appear under Network & Security → Load Balancer in your billing summary. Backends are billed separately as the VMs they are; deleting a load balancer doesn’t delete them.
