Load Balancer Documentation
Use these guides to plan, create, manage, and troubleshoot Load Balancers in MyAccount. Most workflows start from Compute > Load Balancer in the left navigation.
A Load Balancer distributes incoming traffic across a group of backend nodes so your application stays available, scales with demand, and tolerates the failure of an individual server. E2E Cloud offers two types: an Application Load Balancer (ALB) that works at Layer 7 for HTTP and HTTPS traffic, and a Network Load Balancer (NLB) that works at Layer 4 for TCP traffic. If you are not sure which one you need, start with Choose a Load Balancer.
Plan and Launch
Understand ALB vs NLB, scheme, routing policies, and plans before launch.
Launch a Layer 7 ALB with HTTP/HTTPS listeners, backends, and health checks.
Launch a Layer 4 TCP NLB with a listening port and backend servers.
Operate
Start, power off, upgrade, convert to committed, manage committed settings, and delete.
Hub for the Info, Backend, ACL, Network, Monitoring, Security, Logs, and Actions tabs.
Review details and edit name, protocol, SSL, timeouts, BitNinja, and access logs.
Add, edit, and remove backend groups and servers; routing policy and health checks.
Route ALB requests by path, host, query, method, or source IP to backend groups.
Manage the public IP, IPv6, and attached VPCs.
View graphs, configure alerts, and read live HAProxy and Prometheus stats.
Attach, review, and detach security groups and their rules.
Read action logs, billing logs, and the activity timeline.