Auto scaling management
We are preparing a localization service for the content. We will do our best to provide the localization service as soon as possible.
My Server image+Init-Script
- Enables the creation of new servers through my server image
- Provides a first-time script feature to automate server setup after server creation
My Server Image + Init-Script (bootstraping) + Auto Scaling → Automate application installation and system setup on user OS images
- Automate all procedures to put/exclude servers in Load Balancer
- Check the health of servers in the Auto Scaling Group using Load Balancer Health-Check
- Launch Configuration Status: You can check Auto Scaling Group and the currently set Launch Configuration and change Launch Configuration.
- Scaling policy settings status: When monitoring events occur, virtual servers can be created or returned according to the Scaling policy. You can set the Scaling policy, and you can choose between the increment/ratio change/fixed value. You can modify, delete, and execute the generated Scaling.
Set monitoring event settings by referring to "Auto Scaling Monitoring" in the
- Schedule status: You can create or return a virtual server at a predetermined time by the customer. You can set Scaling policies and schedules, such as minimum/maximum/expecting capacity. You can also modify and delete schedules that you create.
- History check: You can check the history of Auto Scaling in detail.
- Notification Settings: Auto Scaling allows you to set the notification target and notification method (mail/SMS) when an event occurs.
- Check the list of servers: A list of servers belonging to the Auto Scaling Group can be found.
- Process Management : You can view and change the process status of Auto Scaling Group. You can pause and restart.
- Change of increase or decrease: This method directly adds or deletes the specified number of servers regardless of the current group size.
- Ratio change: This method increases or decreases the server by a certain percentage of the current group size.
- Fixed Value : The method of holding the group size to the specified value.
|Specifications and Service Environment Limits||- Only servers with a total disk size of 150GB or less
- Windows OS only supports Windows 2012. 2016
- For my server image, support only if the boot disk size on the source server is 50GB (only later for 100GB disks).
|Config Limits||- Maximum number of Auto Scaling Groups per customer: 100
- Maximum number of Launch Configurations per customer: 100
- Maximum number of scheduled actions that can be created per Auto Scaling Group: 100
- Maximum number of Scaling Policies can be created per Auto Scaling Group: 10
- Maximum number of servers that can be created per Auto Scaling Group: 30
-Maximum number of load balancers can be connected per Auto Scaling Group :10
The maximum number of servers that can be created per account on the Naver Cloud platform is 50 by default. To adjust the number of servers limit, please contact Customer Support > Contact.
|Scale-in / Scale-out||Auto Scaling Group을 생성하여 고객이 설정한 Policy에 따라 사용하고 있는 가상 서버의 자동 확장(Scale-out) 및 자동 축소(Scale-in)하도록 제공합니다.|
|Auto Scaling Group||Multiple server instances are grouped together into one group called the Auto Scaling Group.|
|Launch Configuration||The template that Auto Scaling Group uses to start up and configure virtual servers. When you create an Auto Scaling Group, you must specify Launch Configuration.|
|Auto Scaling Group Minimum/Maximum Capacity||Refers to the minimum/maximum number of servers in the Auto Scaling Group. For the minimum number of servers, the number of servers that are equal to or greater than this is always maintained. Set to 0 to allow no servers to be retained.|
|Desired Capacity||The number of servers is adjusted according to the expected capacity value. This value must be at least the minimum and at least the maximum. If this value is not specified, initially create a minimum capacity server.|
|(Default Cooldown)(sec)||Default Cooldown (seconds) Even if a new server is created, it may take some time for the actual service to be ready to be performed, for example, by running Init-Script or installing updates. Cooldown time is the period that you set to ignore even when monitoring event alarms occur during or after actual Scaling.|
|Health Check||Perform periodic health checks on the virtual servers in the Auto Scaling Group to check their health to identify unhealthy virtual servers.|
|Health Check Hold Period||Even if the server is created and changed to 'In Operation', operations such as installing updates on the server may fail to respond normally to health checks. In this case, if you specify a health check hold period, the server health will not be judged to be abnormal even if the health check fails during that period.|
|health check type||You can choose between the server and Load Balancer. If you specified the Load Balancer name in Auto Scaling Group settings, set the health check type to Load Balancer as well. In this case, Auto Scaling determines the status of the server based on the Load Balancer health check method and criteria.|
|Termination Policy||For scale-in operations on servers added during Auto Scaling, customers can first specify which servers to return in API query format. The default settings are returned to the server that was created first.|
|Policy||AWe define how Auto Scaling happens, which we define as 'Policy'. Defines how many virtual servers to increase when Auto Scale-out occurs, or how many virtual servers to reduce when Scale-in occurs. You can define it as a algebraic number, or you can define it as a percentage.|