The page has been translated by Gen AI.

Overview

Service Overview

The Load Balancer (LB) service of Samsung Cloud Platform automatically distributes traffic to available servers when there is an unpredictable traffic surge or server failure, ensuring the stability and continuity of customer services.

A Load Balancer serves as the service endpoint provided to clients, is deployed in a VPC subnet according to the service type (L4 / L7), and you can configure multiple services by adding listeners to the created Load Balancer.

The Listener receives client requests through the service port and processes traffic according to routing rules. L4 supports TCP / UDP / TLS protocols, and L7 supports HTTP / HTTPS protocols; in L7, you can specify an LB server group for each routing condition or set a redirect response for the request URL.

The LB server group forwards requests received by the Listener to specific servers based on load balancing and health checks. The servers receive client requests from the Load Balancer’s Source NAT IP through the ports configured for the members, and the server status is periodically monitored by the Load Balancer’s health check IP.

LB health check defines the member health check method registered in the LB server group. You can select a default LB health check resource provided for the LB server group, or create a new one to configure monitoring suitable for the application.

Features

  • Various load balancing methods: Round Robin, Least Connection, IP Hash, etc., are provided.
  • SSL Authentication Encryption and Offloading: Supports SSL offloading and allows selection of encryption level.
  • Enhanced Security: Use a firewall to manage Load Balancer communication and view connection logs by storing logs.

Service Architecture Diagram

Diagram
Figure. Load Balancer diagram

Provided features

  • Load Balancer: Select the service type and configure the IP to be used by the Load Balancer.
  • Listener: Set the protocol, port, and routing rules. You can add multiple Listeners to a single Load Balancer.
  • LB server group: Sets the load balancing method. LB server group can be attached to a single Load Balancer.
  • Member: Select the server to add to the LB server group. You can choose Virtual Server or Bare Metal Server resources created in the same VPC as the Load Balancer, or enter an IP address directly.
  • LB health check: Sets the member health check method. LB health checks can be registered and used across multiple LB server groups.

Component

A Load Balancer consists of a Load Balancer (Listener), LB server group (member), and LB health check.

Load Balancer

The components that make up a Load Balancer are as follows. By configuring each component, you can set up load balancing suitable for the customer’s workload.

ComponentDetailed description
Service CategoryLoad Balancer service type
  • Classification of Listener protocols that can be created according to L4 / L7
Service SunbetAssign the Service IP, Source NAT IP, and Health Check IP required for the Load Balancer in the Subnet range of the VPC Subnet
  • Subnet
Service IPService IP that the client accesses
Source NAT IPIP used to forward server traffic in the Load Balancer
Health check IPIP used for health checks in the Load Balancer
ListenerResources connected to the Load Balancer
  • protocol, port, LB server group settings
Table. Load Balancer components

LB server group

The elements that make up an LB server group are as follows. Traffic is delivered to members of the LB server group according to the settings of each component.

ComponentDetailed description
ProtocolLB server group forwarding protocol
Load balancingTraffic distribution method
  • Deliver traffic to a specific member according to the load balancing method
LB health checkMember health check method
  • LB Select from the list of resources created by the health check
MemberServer that processes client requests
  • Set weights or modify activation status based on load balancing
Table. LB server group components

LB health check

The elements that make up the LB health check are as follows. Member health checks are performed according to the settings of each component.

ComponentDetailed description
ProtocolHealth check protocol
Health check portPort used for health check
PeriodHealth check execution interval
Waiting timeServer response latency for health check
Detection countCriteria for determining member health check status (Healthy / Unhealthy)
Table. LB health check components

Constraints

The Load Balancer of Samsung Cloud Platform has a default quota, which limits the number of Load Balancers, Listeners, LB server groups, and members that can be created. You can manage current usage through the Console and request additional quota for items that can be expanded.

ItemDefault quotaDetailed description
LOAD_BALANCER.SERVICE_SUBNET.DEFAULT.COUNT3Number of Service Subnets per VPC that can create a Load Balancer
LOAD_BALANCER.DEFAULT.COUNT50Number of Load Balancers created per Region
LOAD_BALANCER.LISTENER.DEFAULT.COUNT1000Number of Listeners created per Region
LOAD_BALANCER.SERVER_GROUP.DEFAULT.COUNT1000Number of LB server groups created per region
LOAD_BALANCER.MEMBER.DEFAULT.COUNT1000Number of members that can be registered to the entire LB server group per region
LOAD_BALANCER.HEALTH_CHECK.DEFAULT.COUNT500Number of LB health checks created per region
Table. Load Balancer Constraints

Preliminary Service

This is a list of services that must be pre-configured before creating a Load Balancer service. Please refer to the guide provided for each service and prepare in advance.

Service CategoryServiceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. Load Balancer prerequisite service
Release Note
ServiceWatch metric