Home Load Balancers & TLS Create a load balancer

Create a load balancer

Last updated on Nov 02, 2026

A load balancer gives your service one address and spreads incoming connections across several servers. If a server stops answering its health check, traffic goes to the others, so one failed server does not take your service down.

What it does

  • It balances TCP and UDP traffic: websites, APIs, databases, game servers, DNS, anything that listens on a port.
  • It spreads connections by hashing each client's address and port, so a connection always stays on the same server.
  • It does not decrypt traffic. HTTPS passes straight through to your servers, so each server holds the certificate and answers HTTPS itself. See Turn on HTTPS (free certificate).
  • Its health check tests the connection (TCP or UDP). It does not load a web page.
  • Your servers see each visitor's real IP address.

Before you start

Have at least two servers running the same application, in the same region and on the same private network.

Create it

  1. In the console menu open Networking, then Load Balancers, and click Create Load Balancer.
  2. Deployment region: choose the region your servers are in (Kigali, Huye or Nairobi).
  3. Basics:
    • Name: for example web-lb.
    • Provider: if more than one is listed, choose the one described as Lightweight L4 (TCP/UDP). This article describes that load balancer.
    • VIP network: the private network your servers are on. The load balancer takes its address from this network.
  4. Listener:
    • Protocol: TCP for websites (HTTP and HTTPS), APIs and most applications. UDP for services such as DNS or voice.
    • Port: the port clients connect to, for example 443 for HTTPS.
  5. Balancing method: set for you. Connections are spread by client address and port; there is nothing to choose.
  6. Targets: tick the servers that should receive traffic. Only servers on the VIP network are listed, and you can add them later. Traffic goes to the same port on each server. If your servers listen on a different port, switch to Advanced at the top of the page and set Target port.
  7. Health check: leave it on and choose TCP for a TCP listener or UDP for a UDP listener. A server that stops answering is taken out of rotation until it recovers. Advanced lets you change the timing.
  8. Check the cost on the right and click Create load balancer.

Make it reachable from the internet

The load balancer starts with a private address only.

  1. On the Load Balancers list, open the menu on its row, choose Associate Floating IP and pick a public IP.
  2. Because your servers see the visitor's real address, open the listener's port in the security group of each target server, for the addresses that should reach it (for a public website, from anywhere). See Open a port.

Good to know

  • For real redundancy, put the target servers in an anti-affinity placement group so they never share a host. See Keep servers together or apart.
  • Behind a load balancer, install the HTTPS certificate on every target server, not on the load balancer.
  • If traffic does not arrive, check the security groups on the target servers first. See My server cannot be reached.