Create a Load Balancer
In the menu, select Load Balancer > Load Balancer, then click Create Load Balancer. The console opens a 5-step wizard:
- Basic Information
- Server Pool & Health Check
- Listener
- Recommended alarm
- Review & Create
The system creates one default Server Pool and one default Listener from the values you provide in the wizard.
Step 1. Basic Information
| Field | Description |
|---|---|
| Name | Name of the Load Balancer. Only letters, numbers, underscore, hyphens, spaces, and dot are allowed. Can be changed later. |
| Description | Optional description. |
| Tags | Optional tags applied to the Load Balancer. |
| Subnet | The network for the Load Balancer. Select an existing subnet from the list, or leave blank if no specific network planning is required. |
| Public IP | Assign a public IP if the Load Balancer must be reachable from the internet. Default is None (internal Load Balancer). |
| Private IP | Enter a specific private IP within the subnet. Leave blank to assign one automatically. |
Size
Select the package that suits your workload. All packages are high-availability (24/7).
| Size | High Availability | Active Connection | Application Throughput |
|---|---|---|---|
| Starter | Yes | 500 | 2,000 requests/s |
| Basic-1 | Yes | 1,000 | 5,000 requests/s |
| Basic-2 | Yes | 2,000 | 10,000 requests/s |
| Standard | Yes | 4,000 | 20,000 requests/s |
| Advanced-1 | Yes | 6,000 | 30,000 requests/s |
| Advanced-2 | Yes | 8,000 | 40,000 requests/s |
| Premium | Yes | 12,000 | 80,000 requests/s |
Click Next to continue.
Step 2. Server Pool & Health Check
Server Pool
| Field | Description |
|---|---|
| Server pool name | Name of the Server Pool. Default is Default server pool. |
| Description | Optional description. |
| Protocol | Protocol the Server Pool uses (for example, HTTP). |
| TLS | Enable TLS for a secure connection with backend servers. Enable when the Listener uses the TERMINATED_HTTPS protocol. |
| Add server | Add members to the pool — choose instances within the VPC or add an external member (Instance, IP Address, Subnet, Port, Weight). |
Advanced Settings
| Field | Description |
|---|---|
| Algorithm | Request-distribution algorithm: Round Robin, Least Connection, or Source IP. |
| Sticky session | Keep a client's requests on the same server: None, App Cookie, HTTP Cookie, or Source IP. |
Health Check Settings
| Field | Default | Description |
|---|---|---|
| Protocol | HTTP | Protocol of the health monitor. |
| URL Path | / | Must begin with a forward slash (/). |
| HTTP Method | GET | HTTP method used for health-check requests. |
| Expected Code | 200 | HTTP status codes that declare a member healthy. |
| Max retries down | 3 | 1–10. Failed checks before a member is marked down. |
| Max retries | 3 | 1–10. Successful checks before a member is marked up. |
| Delay (s) | 5 | Time between probes. |
| Timeout (s) | 5 | Maximum time to wait for a probe response. |
Click Next to continue.
Step 3. Listener
| Field | Description |
|---|---|
| Listener name | Name of the Listener. Default is Default listener. |
| Description | Optional description. |
| Protocol | Protocol the Listener uses to receive requests. |
| Port | Port the Listener listens on (for example, 80). |
| Server pool | The pool that requests are routed to (linked to the pool from Step 2). |
| Allow CIDRs | CIDRs allowed to access this Listener. All other traffic is denied. One CIDR per line. Default 0.0.0.0/0. |
| Deny CIDRs | CIDRs denied access, even if included in the allow list. One CIDR per line. |
| HTTP Headers insertions | Headers inserted into requests to members: X-Forwarded-For, X-Forwarded-Port, X-Forwarded-Proto. |
Advanced Settings
| Field | Default | Description |
|---|---|---|
| Member connect timeout (s) | 5 | Backend member connection timeout. |
| Client data timeout (s) | 50 | Frontend client inactivity timeout. |
| Member data timeout (s) | 50 | Backend member inactivity timeout. |
| TCP inspect timeout (s) | 0 | Time to wait for additional TCP packets for content inspection. |
| Connection limit | -1 | Maximum connections for this Listener. -1 means unlimited. |
Click Next to continue.
Step 4. Recommended alarm
The wizard suggests two Cloud Guard alarms to detect overload conditions:
| Alarm | Metric | Condition |
|---|---|---|
| Active connection | Active connection | Greater than 1,000 |
| Drop packet | Drop packet In/Out per second (packet/s) | Greater than 50 |
For each alarm, select a Notify to recipient (required if you keep the alarm). If you do not have a recipient yet, use Create recipient here to add one (Email, Telegram, Slack, and Teams are supported). Remove an alarm with its delete icon if you do not want it.
Click Next to continue.
Step 5. Review & Create
Review the full configuration (read-only). To change anything, click Previous. When ready, click Create Load Balancer.
Check the status
After creation, the console returns to the Load Balancer list. Each Load Balancer, Listener, Server Pool, and Member has its own status.
| Object | Provisioning status | Operating status |
|---|---|---|
| Load Balancer | Active: created successfully. Creating: initialising. Updating: being updated. Deleting: being deleted. Error/Pending: an error occurred — contact support. | Healthy: all members healthy. Unhealthy: at least one member unhealthy. Offline: all members unhealthy. No healthcheck: no health check configured. |
| Listener | Same as Load Balancer | N/A |
| Server Pool | Same as Load Balancer | Same as Load Balancer |
| Member | N/A | Healthy: available to receive requests. Unhealthy: unavailable. |
The list also shows the Public IP, Private IP, Tags, Size, and Created at of each Load Balancer.
Load Balancer creation may take a moment. Wait until the provisioning status is Active before continuing.