Auto scaling group

Available in VPC

The following describes how to create an Auto Scaling Group based on launch configurations.

Auto Scaling Group screen

The basic description for the use of an Auto Scaling Group is as follows:

Check Auto Scaling Group list

You can check information on each Auto Scaling Group. The following describes how to view the information.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. When the Auto Scaling Group list appears, check the summary information or click an Auto Scaling Group to check the details.
   • Auto Scaling Group name: the name entered when creating the Auto Scaling Group
   • Launch Configuration name: the name of the launch configuration specified for the Auto Scaling Group
   • Hypervisor: the base hypervisor for Auto Scaling servers
   • Minimum capacity: the minimum number of servers of the Auto Scaling Group
   • Maximum capacity: the maximum number of servers of the Auto Scaling Group
   • Desired capacity: the desired number of servers of the Auto Scaling Group. If not entered, servers are created according to the minimum capacity.
   • Number of servers: the current number of servers
   • Health check type: health check standard of the Auto Scaling Group
   • Server name prefix: the prefix attached to the Auto Scaling server
   • VPC: the name of the VPC where the Auto Scaling Group is deployed
   • Subnet: the subnet mask where Auto Scaling Group is deployed and its name
   • Access Control Group: the ACG name applied to the Auto Scaling server
   • Server configuration: detailed specifications of the Auto Scaling server
   • Default cooldown value (second): the cooldown time value to apply when performing scaling
   • My Server image: the name of the My Server image used. A blank is displayed if the default image is used.
   • Creation date: the date and time when the Auto Scaling Group was created
   • Health check grace period (second): health check grace period value
   • Target Group: the target group connected when connecting to the load balancer
   • Apply detailed monitoring: whether to monitor the servers created according to the scaling policy

Create Auto Scaling Group

The following describes how to create an Auto Scaling Group on NAVER Cloud Platform's console.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Click the [Create Auto Scaling Group] button.
5. When the Auto Scaling Group creation page appears, take the following steps in order.
   • 1. Select launch configuration
   • 2. Set group
   • 3. Set network access
   • 4. Set up policy/schedule
   • 5. Set notification
   • 6. Final confirmation

1. Select launch configuration

Select the configuration template of the server to be included in the Auto Scaling Group, i.e., select the launch configuration, and click the [Next] button.

2. Set group

Specify the Auto Scaling Group settings information and click the [Next] button.

• Auto Scaling Group name: enter from 1 to 255 English lowercase letters, numbers, and hyphens (-)
• VPC: select the VPC for the Auto Scaling Group
• Subnet: select the subnet mask for the Auto Scaling Group
• Server name prefix: enter the prefix to be attached to the Auto Scaling server
• Minimum capacity: enter the minimum number of servers of the Auto Scaling Group
• Maximum capacity: enter the maximum number of servers of the Auto Scaling Group
• Desired capacity: enter the desired number of servers of the Auto Scaling Group. If not entered, the minimum number of servers are created after the group is created.
• Apply detailed monitoring: select whether to monitor the servers created according the scaling policy. If it is used, it is charged according to the Cloud Insight pricing policy.
• Default cooldown value (second): enter the cooldown time value to wait without reacting to other alarms until the server is fully ready when performing scaling
• Health check grace period: considering the fact that a health check cannot be properly responded to due to an update immediately after server creation, enter a grace period during which there is no problem even if the health check fails
• Health check type: health check standard of the Auto Scaling Group
  • The server is selected by default as the standard for health check, and you can select and connect to the Load Balancer (up to 10 can be connected).
  • When you select Load Balancer, you must enter the health check grace period, and select the target group from Target Group.

3. Set network access

Select the ACG to be applied to the Auto Scaling Group and click the [Next] button.

4. Set up policy/schedule

Set the scaling policy or schedule, and click the [Next] button.

• Set later: set it later, not now
• Set policy: set the policy for increasing/decreasing the number of servers (up to 10 can be created)
  • Policy name: enter the policy name
  • Set scaling: change increase/decrease, change ratio, and set the scaling policy from among fixed values
    • Increase/decrease change: enter the number of servers to increase or decrease
    • Percent change in capacity: enter a certain percentage at which the server increases or decreases in comparison to the current group size
    • Fixed value: enter the fixed value of the group size
  • Minimum adjustment width: you can enter it only when you selected Percentage change in capacity, and it specifies the minimum adjustment width
  • Cooldown (second): enter the waiting time value without reacting to other alarms when scaling is performed
• Set schedule: set the schedule for increasing/decreasing the number of servers (up to 100 can be created)
  • Schedule name: enter the name of the schedule
  • Set scaling: enter the minimum capacity, maximum capacity, or desired capacity for performing scaling
    • You must enter at least one of the three items.
  • Time Zone: select a time zone
  • Start time: enter the date and time to start the schedule. If there is no input, the start date is designated as the earliest iteration schedule after saving the settings.
  • Set repetition: if repeated execution is required, enter the repetition cycle, but enter the same rules as Linux Cronjob
  • End time: when setting repetition, enter the date and time to end the repetition. If not, it is repeated infinitely.

5. Set notification

After setting the event notification function, click the [Next] button.

• Set later: set it later, not now
• Notification details: enable the function to notify when an event occurs
  • Notification details: select an event to be notified
  • Set notification: select the person to be notified
    • You can select only from those registered in the notification target management group
    • To add a new notice recipient, click the [Manage notification recipients] button to add the recipient (see Notification recipient addition guide)

6. Final confirmation

Check the set details and then click the [Create Auto Scaling Group] button.

• A group is created and added to the Auto Scaling Group list.

Integrate monitoring event

If you set the Auto Scaling execution rule as a policy, you can make it so that the Auto Scaling policy is executed based on monitoring events. Just set the Auto Scaling Group as a Cloud Insight monitoring target.
After requesting subscription to Cloud Insight first, set monitoring targets and actions in the Services > Management & Governance > Cloud Insight (Monitoring) > Configuration > Event Rule menu. For more information on the setting method, see Event Rule creation guide.

• An Auto Scaling Group must be created, and there must be a server within the Group.
• As a monitoring metric (performance indicator), items related to CPU usage are mainly used.

Change Auto Scaling Group settings

You can change the policy, schedule, launch configuration, event notification, and detailed process of a created Auto Scaling Group. The following describes how to change.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Select an Auto Scaling Group and click the [Settings] button.
5. Click the setting tab to be changed and change the contents.

   • [Launch Configuration] tab: change the launch configuration connected to the group

   • [Policy] tab: change the scaling policy

     • If you click the [Create] button, a new scaling policy is added (see Set policy)
     • If you click the [Edit] or [Delete] button, you can edit or delete the selected policy, and if you click the [Execute] button, the selected policy is executed immediately

   • [Schedule] tab: set the scaling schedule

     • If you click the [Create] button, a new scaling schedule is added (see Set schedule)
     • When the [Edit] or [Delete] button is clicked, the selected schedule is edited or deleted

   • [Set notification] tab: change notification events and notification targets

     • To add a new notice recipient, click the [Manage notification recipients] button to add the recipient (see Notification recipient addition guide)

   • [Manage process] tab: check the process status of the group and pause/restart it

     Process	Description
     LAUNCH (LANCH)	When a scale-out (server expansion) condition occurs, check the setting value to create and insert a server When paused, server creation stops, and when restarted, scale-out is performed according to the expected quantity
     TERMINATE (TERMT)	When a scale-in (server reduction) condition occurs, check the setting value and return the server When paused, server return stops, and when restarted, scale-in is performed according to the expected quantity
     HEALTH CHECK (HTHCK)	Check server health every 10 seconds When paused, health check ends, and when restarted, health check resumes from the start point
     REPLACE UNHEALTHY (RPUNH)	If the health check of a specific server fails, the failure history is recorded in the database, periodic monitoring is performed, and the server is replaced with another server When paused, even if health check fails, the server is not returned, and scaling is performed according to the expected quantity. When restarted, the remaining servers with health check failures are returned again.
     SCHEDULED ACTIONS (SCACT)	Scaling is performed according to the registered schedule When paused, even if it is schedule start time, scaling is not performed, and when restarted, scaling is performed according to the schedule Scaling due to health check failure or change in the expected quantity is normally performed regardless of whether the process is stopped or not
     ADD TO LOAD BALANCER (ADTLB)	If the health check type is Load Balancer, the additional created servers are bound to the Load Balancer When paused, binding is not performed, but when restarted, binding is performed only on servers added later (binding is not requested for servers added during the pause)
     ALARM NOTIFICATION (ALMNO)	Scaling execution events according to Cloud Insight alarms are notified to the users When paused, the Cloud Insight alarm is ignored, scaling is not performed, and transmission of notices is stopped. When restarted, Cloud Insight alarms that occur later are delivered and scaling is performed and notified.

Edit Auto Scaling Group information

The following describes how to edit the detailed information of a created Auto Scaling Group.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Select an Auto Scaling Group and click the [Edit] button.
5. Edit the detailed information and click the [OK] button.
   • For more information on each item, see 2. Set group.

Check Auto Scaling Group execution history

The following describes how to check the scaling execution history of the Auto Scaling Group.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Select an Auto Scaling Group and click the [History] button.
5. Check the scaling execution history.
   • If you click a server in the list, you can check more detailed information.

Check servers in Auto Scaling Group

The following describes how to check servers in the Auto Scaling Group.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Select an Auto Scaling Group, and click the [Server list] button.
5. Check the server list.

Delete Auto Scaling Group

The following shows how to delete a created Auto Scaling Group.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Compute > Auto Scaling, in order.
3. Click the Auto Scaling Group menu.
4. Click the Auto Scaling Group to delete and click the [Delete] button.
5. When the Delete pop-up window appears, click the [OK] button.
   • The Auto Scaling Group disappears from the Auto Scaling Group list.