Overview
Service Overview
The Load Balancer (LB) service of Samsung Cloud Platform automatically distributes traffic to available servers when traffic increases unpredictably or server failures occur, ensuring the stability and continuity of customer services.
The Load Balancer is deployed in the VPC Subnet according to the service type (L4 / L7) as a service access point provided to clients, and multiple services can be configured 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 LB server groups according to routing conditions or set redirect responses for request URLs.
The LB server group delivers requests received by the Listener to specific servers according to load balancing and health checks. Servers receive client requests from the Load Balancer’s Source NAT IP through the port set on the member, and the server status is periodically monitored by the Load Balancer’s health check IP.
The LB health check defines the member health check method registered in the LB server group. You can select the LB health check resource provided by default in the LB server group, or create a new one to configure monitoring suitable for your application.
Features
- Various Load Balancing Methods: Provides various load balancing methods such as Round Robin, Least Connection, and IP Hash.
- SSL Certificate Encryption and Offloading: Supports SSL offloading and allows selection of encryption levels.
- Enhanced Security: Manage Load Balancer communication using Firewall and view access logs through log storage.
Service Configuration Diagram
Provided Functions
- Load Balancer: Select the service type and set the IP to use in the Load Balancer.
- Listener: Set the protocol, port, and routing rules. You can add multiple Listeners to a single Load Balancer.
- LB Server Group: Set the load balancing method. The LB server group can be connected to a single Load Balancer.
- Member: Select the server to add to the LB server group. You can select Virtual Server and Bare Metal Server resources created in the same VPC as the Load Balancer, or directly enter an IP.
- LB Health Check: Set the member health check method. The LB health check can be registered and used in multiple LB server groups.
Components
The Load Balancer consists of Load Balancer (Listener), LB server group (member), and LB health check.
Load Balancer
The components that make up the Load Balancer are as follows. According to the settings for each component, you can configure load balancing suitable for customer workloads.
| Component | Description |
|---|---|
| Service Type | Load Balancer service type
|
| Service Subnet | VPC Subnet where the Load Balancer will be deployed
|
| Service IP | Service IP that clients access |
| Source NAT IP | IP used by Load Balancer to deliver server traffic |
| Health Check IP | IP used by Load Balancer for health checks |
| Listener | Resources connected to Load Balancer
|
LB Server Group
The components that make up the LB server group are as follows. According to the settings for each component, traffic is delivered to members of the LB server group.
| Component | Description |
|---|---|
| Protocol | LB server group delivery protocol |
| Load Balancing | Traffic distribution method
|
| LB Health Check | Member health check method
|
| Member | Server that processes client requests
|
LB Health Check
The components that make up the LB health check are as follows. According to the settings for each component, member health checks are performed.
| Component | Description |
|---|---|
| Protocol | Health check protocol |
| Health Check Port | Port used for health check |
| Interval | Health check execution interval |
| Timeout | Server response wait time for health check |
| Detection Count | Criteria for determining member health check status (Healthy / Unhealthy) |
Constraints
Samsung Cloud Platform’s Load Balancer applies basic quotas, so there are constraints on 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 quotas for items that can be expanded.
| Item | Basic Quota | Description |
|---|---|---|
| LOAD_BALANCER.SERVICE_SUBNET.DEFAULT.COUNT | 3 | Number of Service Subnets where Load Balancers can be created per VPC |
| LOAD_BALANCER.DEFAULT.COUNT | 50 | Number of Load Balancers created per Region |
| LOAD_BALANCER.LISTENER.DEFAULT.COUNT | 1000 | Number of Listeners created per Region |
| LOAD_BALANCER.SERVER_GROUP.DEFAULT.COUNT | 1000 | Number of LB server groups created per Region |
| LOAD_BALANCER.MEMBER.DEFAULT.COUNT | 1000 | Number of members that can be registered in all LB server groups per Region |
| LOAD_BALANCER.HEALTH_CHECK.DEFAULT.COUNT | 500 | Number of LB health checks created per Region |
Prerequisite Services
This is a list of services that must be pre-configured before creating the Load Balancer service. Please prepare in advance by referring to the guides provided for each service.
| Service Category | Service | Description |
|---|---|---|
| Networking | VPC | Service that provides independent virtual networks in the cloud environment |