How load balancing works - Load Balancer service

The Load Balancer service distributes incoming network connections from client applications to Storage Nodes. It is included on Admin Nodes and Gateway Nodes. To enable load balancing, you must configure load balancer endpoints using the Grid Manager.

Each load balancer endpoint specifies a port, a protocol (HTTP or HTTPS), and a service type (S3 or Swift). HTTPS endpoints require a server certificate. You can configure load balancer endpoints only for Admin Nodes or Gateway Nodes. You cannot configure them for Storage Nodes or Archive Nodes since these nodes do not include the Load Balancer service.

The Load Balancer service on each Admin Node and Gateway Node operates independently when forwarding S3 or Swift traffic to the Storage Nodes.
Attention: If you have remapped any ports, you cannot use the same ports to configure load balancer endpoints. You can create endpoints using remapped ports, but those endpoints will be remapped to the original CLB ports and service, not the Load Balancer service. Follow the steps in the recovery and maintenance instructions for removing port remaps.
Note: Clients can access any of the endpoints you configure on any node running the Load Balancer service, with two exceptions: ports 80 and 443 are reserved on Admin Nodes, so endpoints configured on these ports support load balancing operations only on Gateway Nodes.