Something went wrong
Load balancer type
Select the location where you want to create your load balancer.
Details
If your user tags are billing related, consider writing tags as key:value pairs, such ascostctr:124
User tags are visible account-wide. Avoid including sensitive data in the tag name.Learn more
Back-end pools
Creating a back-end pool from the provisioning page is optional. You can create one later from the load balancer details view after it has been provisioned. Regardless of how you create the pool, you must do so in order for your load balancer to function correctly.
Name | Pool protocol | Method | Health path | Members |
|---|
Front-end listeners
Creating a front-end listener from the provisioning page is optional. You can create one later from the load balancer details view after it has been provisioned. Regardless of how you create the listener, you must do so in order for your load balancer to function correctly.
Listener protocol | Listener port | Certificate | Timeout (second) | Back-end pool |
|---|
Security groups
Select at least one and at most five security groups to control traffic at the networking level.
Click to sort rows by Name header in ascending order | Click to sort rows by Inbound rules header in ascending order | Click to sort rows by Outbound rules header in ascending order | |
|---|---|---|---|
- Data processed - The amount of data processed by the load balancer per hour in GBs.
- Instance hours - The time that your load balancer instance is up and running.
- Data processed - The amount of data processed by the load balancer per hour in GBs.
- Instance hours - The time that your load balancer instance is up and running.
- Data processed - The amount of data processed by the load balancer per hour in GBs.
- Instance hours - The time that your load balancer instance is up and running.
Additional charges
Summary
Deploy IBM Cloud Load balancer for VPC in front of application servers to distribute incoming user traffic, providing protection against failure of an individual application server instance. You can seamlessly scale your applications by adding or removing servers. with minimal to no disruption to existing traffic flows.
Application load balancer (ALB)
Both public and private ALBs provide layer-7 and layer-4 load balancing on IBM Cloud, supporting SSL offloading. The incoming and outgoing packets flow through the load balancer, which distributes data traffic based on configured policies and rules. When incoming requests match the rules that are associated with a policy, that policy defines how the load balancer distributes its traffic.
Network load balancer (NLB)
An NLB provides only layer-4 load balancing on IBM Cloud, and does not support SSL offloading. The NLB is zonal, which means that the members must be in the same zone as the load balancer. The client sends public network traffic to the NLB, which forwards it to its targets. These targets then respond directly to the client by using Direct Server Return (DSR). The load balancer does not perform a check on the contents of the packet. Since Layer 4 network load balancing only processes ingress traffic, it is ideal for workloads that require high throughput and low latency.
Features
Quickly detect server failures
Easily manage your configuration by using the graphical interface or API to monitor your server health and protect against individual server failure.
Intelligent traffic distribution
Balance traffic between available resources to improve uptime and avoid slow data transfer times for users.
Flexible deployment and pricing
Choose the service features and pricing models that are best suited for your unique needs and workloads.
Pricing
To estimate pricing while you create a load balancer, use the "Add to estimate" button on the Create tab.