Configure Load Balancer
Create and configure a new load balancer for your infrastructure
New: Load balancers now support WebSocket and gRPC protocols natively. Configure sticky sessions with cookie-based persistence.
✓
Basic Info
›
2
Configuration
›
3
Backend Pool
›
4
Health Checks
›
5
SSL / TLS
›
6
Review & Deploy
Basic Information
Define the identity and placement of your load balancer
Unique name for identification. Only lowercase letters, numbers, and hyphens.
Tags help organize and filter resources. e.g., environment:production, team:platform
Protocol & Algorithm
Choose how traffic is distributed across your backend servers
HTTP / HTTPS
Layer 7 — Web traffic, path-based routing
TCP / UDP
Layer 4 — Raw TCP/UDP proxy
WebSocket
Bi-directional real-time connections
Port the load balancer listens on for incoming traffic
Port on backend servers where traffic is forwarded
Leave blank to use backend port
Backend Server Pool
Add servers that will receive the distributed traffic
Ensure all backend servers are in the same VPC or have network connectivity to the load balancer. Servers will be health-checked before receiving traffic.
| Server | Status | Weight | Region | |
|---|---|---|---|---|
|
10.0.1.15
api-server-01
|
● Healthy |
|
us-east-1 | |
|
10.0.1.16
api-server-02
|
● Healthy |
|
us-east-1 | |
|
10.0.2.22
api-server-03
|
● Initializing |
|
us-west-2 |
Advanced Options
Sticky sessions, timeouts, and traffic management
Sticky Sessions (Session Affinity)
Route requests from the same client to the same backend server using cookies
Cross-Zone Load Balancing
Distribute traffic evenly across all availability zones, regardless of where traffic arrives
Connection Draining
Allow existing connections to complete when a server is removed from the pool
Proxy Protocol (v2)
Passthrough client IP address and connection info to backend servers
Access Log Streaming
Stream real-time access logs to your monitoring system
Rate Limiting
Protect backend services by limiting requests per second per client IP
Seconds to allow existing connections to finish
Health Checks
Configure how the load balancer monitors backend server health
Load Balancer
Initiates check
→
Health Check
HTTP GET /health
→
Backend Server
Expected: 200 OK
The endpoint the load balancer pings to check health
Seconds between checks
Seconds before check times out
Consecutive failures before marking unhealthy
Consecutive successes before marking healthy
SSL / TLS Configuration
Manage certificates and encryption for your load balancer
Terminate at LB
SSL terminated at load balancer, HTTP to backend
Pass-Through
Forward encrypted traffic to backend as-is
Re-Encrypt
Terminate and re-encrypt with backend cert
Drag & drop your certificate or browse files
.pem, .crt, .cer files supported. Private key and full chain required.
31536000 = 1 year. Enable Strict-Transport-Security header.
Access Control
Whitelists, rate limits, and security policies
IP Whitelist
Only allow traffic from specified IP addresses or CIDR ranges
DDoS Protection (WAF)
Automated DDoS mitigation and web application firewall rules
One CIDR range per line. Use 0.0.0.0/0 to allow all IPs.
Max requests per second per client IP