E2E CloudLoad Balancer
A load balancer gives your users one address and spreads their traffic across a group of backend servers. It sends traffic only to the servers that pass their health checks, so one server going down leaves the others serving. You create and manage it in MyAccount, under Compute, on the Load Balancers page.
Each load balancer runs in one region, Delhi or Chennai, and you manage it entirely from MyAccount or the API.
Choose an ALB or an NLB
Section titled “Choose an ALB or an NLB”E2E offers two types, and you choose one when you create the load balancer:
| Type | Works at | Traffic | Sends requests by | Also offers |
|---|---|---|---|---|
| Application Load Balancer (ALB) | Layer 7 | HTTP and HTTPS | The request itself: its path, host, query, method, or client IP | An SSL certificate, ACL rules, HTTPS to your servers, and a scale group as a backend |
| Network Load Balancer (NLB) | Layer 4 | TCP | The port the client connects to | A backend group for each listening port |
Choose an ALB for websites and HTTP APIs, especially when you want HTTPS on the load balancer or want to send different paths or domains to different servers. Choose an NLB for any other TCP service, such as a mail server or a message queue. An NLB passes encrypted traffic to your servers as it is, so the certificate stays on your servers.
Choose external or internal
Section titled “Choose external or internal”- An External load balancer gets a public IP when you create it. Point your domain at that IP with an A record.
- An Internal load balancer has no public IP. It sits in at least one of your VPCs, and resources in that VPC reach it at its VPC address.
What you can do
Section titled “What you can do”- Create an Application Load Balancer for HTTP and HTTPS traffic, with its plan, backend servers, and options.
- Create a Network Load Balancer for TCP traffic on the ports you choose.
- Manage backend groups and servers, with their health check and routing policy.
- Route requests with ACL rules to send paths, domains, or methods to different backend groups.
- Add an SSL certificate to serve HTTPS, redirect HTTP to HTTPS, and renew the certificate.
- View and edit a load balancer’s details: its name, its timeouts, and BitNinja.
- Manage a load balancer’s network and security groups: its VPCs, reserved IP, and firewall rules.
- Monitor a load balancer: its status, graphs, alerts, live statistics, and logs.
- Save access logs to a bucket in E2E Object Storage.
- Power off, start, or upgrade a load balancer.
- Use committed billing for a load balancer you plan to keep.
- Delete a load balancer, and keep its public IP if you want.
- Work with load balancers from a script, with the MyAccount API.
Where to start
Section titled “Where to start”To put your first load balancer in front of a node, follow Get started with Load Balancer. For fixes, see Troubleshooting Load Balancer; for short answers, see Load Balancer FAQ, including what a load balancer costs.