Load Balancer overview

Available in Classic and VPC

Load Balancer is a service that distributes received traffic to multiple servers. It distributes received traffic to registered member servers to increase availability and adjusts the system operation rate. This increases the workload's availability to support responding to unexpected server failures or scheduled change tasks without interruption.
Classic Load Balancer is provided in the Classic environment, and Application Load Balancer, Network Load Balancer, and Network Proxy Load Balancer is provided respectively in the VPC environment, so you can select a suitable Load Balancer for customer service.

Load Balancer features

Features provided by each Load Balancer type and environment are different.
See VPC environment for features provided in the VPC environment, and Classic environment for features provided in the Classic environment.

VPC environment

Load Balancer provides the following features in the VPC environment:

• High-performance load balancing (Network Load Balancer): specialized in high-capacity load balancing, and automatically adjusts performance based on the scale of your service
• TCP session management (Network Proxy Load Balancer): provides communications with proxy methods that can be used in TCP-based applications
• SSL authentication and encryption settings (Application Load Balancer and Network Proxy Load Balancer): provides the SSL protocols, including TLSv1/TLSv1.1/TLS1.2. You can manage the certificates by integrating them with Certificate Manager
• Various server load balancing methods (Application Load Balancer and Network Proxy Load Balancer): provides 3 server load balancing methods
  • Round robin (rounding order)
  • Least connection (minimum connection)
  • Source IP hash (IP hash)
• L7 (Application Layer) feature provision (Application Load Balancer): this is a rule supported by Load Balancer. It segments client requests and forwards them to servers.
• Inline mode provision (Inline Load Balancer): operates in an Inline manner in which network packets must be transferred without tampering, and used to ensure the stability of security appliances in SFC
• Load Balancer monitoring: provides the collected monitoring information by scheduled cycle
• Load Balancer port settings: multiple Load Balancer rules can be applied at once.

Classic environment

Load Balancer provides the following features in the Classic environment:

• SSL authentication and encryption settings: you can manage and apply the certificates to Load Balancers by integrating with Certificate Manager.
• Load Balancer port settings: multiple Load Balancer rules can be applied at once.
• Load Balancer monitoring: provides the collected monitoring information by scheduled cycle
• Load Balancer management: after creating a Load Balancer, you can change the Connection Idle Time (connection hold time with Load Balancer) and Keep-Alive (reusing the existing connection) settings.
• Various server load balancing methods: provides 3 server load balancing methods
  • Round robin (rounding order)
  • Least connection (minimum connection)
  • Source IP hash (IP hash)

Load Balancer user guide

Load Balancer is available in Korea, Singapore, U.S. West, Japan, and Germany Regions. Because service details vary in each Region, we provide the user guides by different Regions as the following:

• Korea, Singapore, and Japan Regions
• U.S. West, Japan, and Germany Regions

Korea, Singapore, and Japan Regions

This guide will walk you through the information you need to start using Load Balancer in the Korea, Singapore, and Japan Regions.

• Load Balancer overview: describes features, user guides, related resources, and FAQs
• Load Balancer specifications: the specifications, service limits, and pricing information for using Load Balancer
• Load Balancer quickstart: guides you through the entire process step-by-step
• Getting started with Load Balancer (VPC): learn the preparations for using Load Balancer, how to create target groups, and how to create Load Balancers
• Using Load Balancer (VPC): describes how to use Load Balancer in the VPC environment
  • Target Group screen: describes the Target Group screen
  • Create and manage Target Group: describes how to create, delete, and manage Target Groups
  • Load Balancer screen: describes the Load Balancer screen provided in the VPC environment
  • Create and manage Application Load Balancer: describes how to create, delete, and manage Application Load Balancers
  • Create and manage Network Load Balancer: describes how to create, delete, and manage Network Load Balancers
  • Create and manage Network Proxy Load Balancer: describes how to create, delete, and manage Network Proxy Load Balancer
  • Using multiple certificates: describes how to use multiple TLS/SSL certificates
• Load Balancer permissions management (VPC): manage accounts using NAVER Cloud Platform's Sub Account
• Getting started with Load Balancer (Classic): learn the preparations for using Load Balancer, how to create Load Balancers, and how to change the status of Load Balancers
• Using Load Balancer (Classic): learn how to access Load Balancer in the Classic environment
  • Load Balancer screen: describes the Load Balancer screen provided in the Classic environment
  • Create and manage Load Balancer: describes how to create, delete, and manage Load Balancers in the Classic environment
• Load Balancer glossary: familiarize yourself with key terms and definitions
• Load Balancer release notes: see documentation history for Load Balancer user guides

U.S. West and Germany Regions

This guide will walk you through the information you need to start using Load Balancer in the U.S. West, Hong Kong, and Germany Regions:

• Load Balancer overview: describes features, user guides, related resources, and FAQs
• Load Balancer specifications: the specifications, service limits, and pricing information for using Load Balancer
• Load Balancer quickstart: guides you through the entire process step-by-step
• Getting started with Load Balancer (Classic): learn the preparations for using Load Balancer, how to create Load Balancers, and how to change the status of Load Balancers
• Using Load Balancer (Classic): learn how to access Load Balancer in the Classic environment
  • Load Balancer screen: describes the Load Balancer screen provided in the Classic environment
  • Create and manage Load Balancer: describes how to create, delete, and manage Load Balancers in the Classic environment
• Load Balancer glossary: familiarize yourself with key terms and definitions
• Load Balancer release notes: see documentation history for Load Balancer user guides

Load Balancer related resources

We offer various related resources as well as user guides for you to better understand Load Balancer. If you're a developer or marketer in need of details while you're considering applying Load Balancer or establishing data related policies, make good use of the following resources:

• Improvements in comprehension and usage methods for Load Balancer

  • Load Balancer (VPC) APIs guide: how to use API in the VPC environment for Load Balancer developers
  • Load Balancer (Classic) APIs guide: how to use API in the Classic environment for Load Balancer developers
  • Load Balancer CLI guide: how to use CLI for Load Balancer developers
  • Load Balancer easy start guide: how to distribute web service traffic using Auto Scaling and Load Balancer
  • Ncloud user environment guide: user guide on the VPC and Classic environments and supported features
  • Price introduction, characteristics, and detailed features: summary of Load Balancer's pricing plans, characteristics, and detailed features
  • Latest service news: the latest news on Load Balancer
  • FAQs: frequently asked questions from Load Balancer users
  • Contact us: send direct inquiries in case of any unresolved questions that aren't answered by the user guides

• User guides for integrated services required to use Load Balancer

  • Server creation guide: how to create a Server to bind to Load Balancer
  • VPC/Subnet user guide: how to create VPC/Subnet for Servers
  • ACG user guide: how to set ACG for Servers
  • Sub Account user guide: how to use Sub Account that helps Load Balancer management and administration permissions management
  • Cloud Log Analytics user guide: how to use Cloud Load Analytics that manages logs of Load Balancer
  • Object Storage user guide: how to use Object Storage where you can permanently store the logs saved in Cloud Load Analytics
  • Certificate Manager user guide: how to register SSL certificates for Load Balancer

Check FAQs first.

Q. How many Load Balancers can I create?
A. You can create up to 50 Load Balancers per Region.

Q. How many servers can I bind to 1 Load Balancer?
A. A Load balancer can bind up to 100 servers.

Q. Can multiple servers be applied to 1 Load Balancer?
A. All servers in multiple zones can be applied to 1 Load Balancer. Also, you can apply the servers applied to other Load Balancers.

Q. How do I set a Load Balancer domain name to the service domain?
A. Set the Load Balancer domain name with the following procedures:

1. Click the Load Balancer where you want to set the domain and view the access information.
2. Click Services > Networking > Global DNS> Record in order.
3. Click the [Add domain] button to add the domain.
4. Click the [Add record] button.
5. Enter the record name and enter the record value according to the following cases:
   • If it is added as A record, enter the Load Balancer IP provided as A record for your service's domain name.
   • If it is added as CNAME record, enter the Load Balancer domain provided as CNAME record for your service’s domain name.
     • Example: if you own example.com domain
       
     • Example: the CNAME for zone apex (-root domain) cannot be registered (RFC1033).
       
6. Click the [Add] button.
   • The IP viewed from the Load Balancer DNS name can change based on scale changes and multi-zone use status. Make sure not to use the viewed IP instead of the provided DNS name to register to the service directly.
   • The DNS names provided through Load Balancer do not change, so the service does not get affected when registered with DNS names.

Q. If I want to define the permissions by action units through the user created policy, do I need to be aware of the relations between actions?
A. When the main account selects specific actions to grant to a sub account, the system offers a feature to automatically select the related actions as well.