Available in Classic and VPC
To use Auto Scaling, you must become familiar with a few terms. The glossary and its description are as follows:Desired Capacity
The standard by which the number of servers is adjusted. This value must be higher than the minimum capacity and lower than the maximum capacity, and if unspecified, servers are created in minimum capacity initially.
Load Balancer (LB)
A NAVER Cloud Platform service that distributes network traffic to multiple servers in consideration of server performance and load
Scale-in / Scale-out
Feature that facilitates the scale-out and scale-in of virtual servers in use according to the policies set by the user by creating an Auto Scaling Group
Launch Configuration
Template used when launching the configurations of the virtual server on Auto Scaling Group. Launch configurations must be specified when an Auto Scaling Group is created.
Auto Scaling
A NAVER Cloud Platform service that facilitates flexible responses to changes in demand by automatically increasing or decreasing the number of virtual servers, according to server group monitoring results or events set by the user in advance
Auto Scaling Group
Numerous server instance groups for using the Auto Scaling
Min/Max Capacity of Auto Scaling Group
The minimum and maximum number of servers of an Auto Scaling Group. The minimum number of servers is always maintained at a value equal to or greater than this value. When it is set to 0, the status of owning no servers can be maintained.
Policy
How Auto Scaling occurs. Defines the virtual server's scope of fluctuations in algebraic numbers or % upon the occurrence of scale-out and scale-in.
Default Cooldown
Default time period of which monitoring event notifications are ignored even if they occur during or after the execution of an actual scaling event, because although newly created, servers require preparation time for actual service execution due to reasons like Init-Script execution or update installation
Health Check
Behavior of executing regular status checks on Auto Scaling Group's virtual servers, checking to distinguish virtual servers in abnormal status
Health Check Grace Period
Period of which servers will not be determined to have abnormalities on server health even if they fail the health check. This can occur when servers are unable to respond normally to the health check due to the occurrence of special occasions like update installations, even though the servers are created and in operation.
Health Check Type
Health check type can be selected between server and load balancer. If in the Auto Scaling Group settings you assign a load balancer name, then the health check type also sets as load balancer. In this case, Auto Scaling will determine server status according to load balancer's health check methods and standards.
To see a full list of terms and definitions, go to Glossary from the NAVER Cloud Platform portal.