Auto Scaling Group

Available in Classic

You can create an Auto Scaling Group based on Launch Configurations.

Auto Scaling Group interface

The Auto Scaling Group interface includes the following components:

View Auto Scaling Group list

You can view information for each created Auto Scaling Group. To view the Auto Scaling Group list:

1. In the Classic environment of the NAVER Cloud Platform console, navigate to > Services > Compute > Auto Scaling.
2. Click the Auto Scaling Group menu.
3. When the Auto Scaling Group list appears, review the summary or click an Auto Scaling Group to view the details.
   • Auto Scaling Group name: The name entered when creating the Auto Scaling Group.
   • Launch Configuration name: The name of the Launch Configuration assigned to the Auto Scaling Group.
   • Minimum capacity: The minimum number of servers in the Auto Scaling Group.
   • Maximum capacity: The maximum number of servers in the Auto Scaling Group.
   • Desired capacity: The desired number of servers in 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: The health check criteria for the Auto Scaling Group.
   • Server name prefix: The prefix added to Auto Scaling server names.
   • Zone(s): The zones where the Auto Scaling Group is deployed.
   • Default cooldown (seconds): The cooldown time applied when scaling is performed.
   • Server configuration: The detailed specifications of the Auto Scaling servers.
   • My server image: The name of the custom server image used. If a default image is used, this field is left blank.
   • Load balancer: The name of the connected Load Balancer when the health check type is set to Load Balancer.
   • Health check grace period (seconds): The grace period applied to health checks.
   • Termination policy: The server termination policy configured when creating the Auto Scaling Group.
   • NAT Gateway: Whether the NAT Gateway is used.
   • Peer Host: The name of the Peer Host used with the NAT Gateway.

Create Auto Scaling Group

To create an Auto Scaling Group in the NAVER Cloud Platform console:

1. In the Classic environment of the NAVER Cloud Platform console, navigate to > Services > Compute > Auto Scaling.
2. Click the Auto Scaling Group menu.
3. Click [Create Auto Scaling Group].
4. When the Create Auto Scaling Group interface appears, complete the following steps in order:
   • 1. Select Launch Configuration
   • 2. Configure group settings
   • 3. Configure policies/schedules
   • 4. Configure notifications
   • 5. Review final settings

1. Select Launch Configuration

After selecting the Launch Configuration, which is the configuration template for the servers to be included in the Auto Scaling Group, click [Next].

2. Configure group settings

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

• Auto Scaling Group name: Enter using 1 to 255 lowercase letters, numbers, and hyphens (-).
• Zone: Select the zone in which to deploy the Auto Scaling Group.
• Server name prefix: Enter the prefix to be added to Auto Scaling servers.
• Minimum capacity: Enter the minimum number of servers in the Auto Scaling Group.
• Maximum capacity: Enter the maximum number of servers in the Auto Scaling Group.
• Desired capacity: Enter the desired number of servers in the Auto Scaling Group. If not entered, the minimum number of servers are created after the group is created.
• Default cooldown (seconds): Enter the cooldown time during which the system waits without responding to other notifications　until the server is fully ready when scaling is performed.
• Health check grace period: Enter the grace period during which a failure in health checks is not considered an issue in consideration of tasks such as updates immediately after server creation that may prevent normal health check responses.
  • This field must be entered when the health check type is set to Load Balancer.
• Health check type: The health check criteria for the Auto Scaling Group. Server is selected by default, and Load Balancer can be selected.
• Load balancer: Select whether to connect a Load Balancer.
  • If you select the option to　Connect to Load Balancer by clicking the check box,　the health check type is set to Load Balancer and you can select the Load Balancer to connect (up to 10 Load Balancers can be connected). When a Load Balancer is selected, Auto Scaling servers are automatically bound to the Load Balancer.
• Termination policy: Configure the server termination policy.
  • Default: Servers are terminated starting with the oldest server among the affiliated servers.
  • Directly specified by the customer through API: The user specifies the termination target through the API.
    • API URL to be called: The API URL that requests the list of servers to be terminated from the user when server termination is required.
    • Response timeout: The time to wait for the user's response. If this time is exceeded, servers are terminated according to the default setting.
    • API authentication (optional): Additional authentication means for the user's API.
• For NAT Gateway: Select whether to use the NAT Gateway.

HTTP query API, LIKE REST API, but not REST
HTTP only, not yet HTTPS
HTTP method: POST
POST body data type: json
{autoScalingGroupName:”asg-1”, terminationCandidateInstances:[{instanceName:”s-1”, instanceNo:”10342”, instanceIpAddress:”10.7.31.4”}], adjustmentMagnitude:2}
Result data type: json
{autoScalingGroupName:”asg-1”, selectedInstanceNoList:[{“10342”, “20024”, “89103”}]}
Size of list must be >= adjustmentMagnitude:2 and <= # of terminationCandidateInstances

3. Configure policies/schedules

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

• Set later: Do not configure now and configure later.
• Configure policy: Configure the server scale-out/scale-in policies (up to 10 policies can be created).
  • Policy name: Enter the name of the policy.
  • Scaling setting: Configure the scaling policy by selecting change in number, change in ratio, or fixed value.
    • Change in number: Enter the number of servers to increase or decrease.
    • Percent change in capacity: Enter the rate at which the number of servers increases or decreases relative to the current group size.
    • Fixed value: Enter a fixed value for the group size.
  • Minimum adjustment size: Available only when　Percent change in capacity is selected, and specifies the minimum adjustment size.
  • Cooldown (seconds): Enter the time during which the system waits without responding to other notifications　when scaling is performed.
• Configure　schedule: Configure the server　scale-out/scale-in schedule (up to 100 schedules can be created).
  • Schedule name: Enter the name of the schedule.
  • Scaling setting: Enter the minimum capacity, maximum capacity, and desired capacity for scaling execution.
    • At least one of the three values must be entered.
  • Time zone: Select the reference time zone.
  • Start time: Enter the date and time to start the schedule. If not entered, the start date is set to the earliest recurring schedule after the settings are saved.
  • Recurrence　setting: If recurrence is required, enter the recurrence cycle using the same rules as Linux Cronjob.
  • End time: When recurrence is configured, enter the date and time to end the recurrence. If not entered, the recurrence continues indefinitely.

4. Configure notifications

After configuring the event notification feature, click [Next].

• Set later: Do not configure now and configure later.
• Notifications: Enable the feature to send notifications when an event occurs.
  • Notifications: Select the events for which notifications will be sent.
    • Administrative Suspension refers to a situation in which the use of the corresponding Launch Configuration is suspended because it is determined to be defective.
  • Notification settings: Select the person in charge to receive notifications.
    • Only recipients registered in the notification target management group can be selected.
    • To add a new notification recipient, click [Manage notification recipients] and add the recipient (see Notification recipient addition guide).

5. Review final settings

After reviewing the settings, click [Create Auto Scaling Group].

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

Monitoring event integration

If you have configured Auto Scaling execution rules as policies, you can set the Auto Scaling policies to run based on monitoring events.
Set the Auto Scaling Group as a Cloud Insight monitoring target.
First, apply to use Cloud Insight, and configure the monitoring target and actions in > Services > Management & Governance > Cloud Insight (Monitoring) > Configuration > Event Rule. For more information on the setting method, see Event Rule creation guide.

• The Auto Scaling Group must be created and servers must exist in the group.
• As monitoring metrics (performance indicators), items related to CPU usage are mainly used.

Configure and view Auto Scaling Group

You can change the policy, schedule, Launch Configuration, event notification, and detailed process of a created Auto Scaling Group. You can also view the scaling execution history of the Auto Scaling Group and the servers that belong to the group. To configure and view an Auto Scaling Group:

1. In the Classic environment of the NAVER Cloud Platform console, navigate to > Services > Compute > Auto Scaling.
2. Click the Auto Scaling Group menu.
3. Select an Auto Scaling Group　and click [Set and manage].
4. Click the tab for the settings you want to change and modify the contents.
   • [Launch Configuration] tab: Change the Launch Configuration associated with the group.
   • [Policy] tab: Change scaling policies.
     • If you click [Create], a new scaling policy is added (see Set policy).
     • If you click [Edit] or [Delete], you can edit or delete the selected policy. If you click [Run], the selected policy is executed immediately.
   • [Schedule] tab: Configure scaling schedules.
     • If you click [Create], a new scaling schedule is added (see Set schedule).
     • If you click [Edit] or [Delete], the selected schedule is edited or deleted.
   • [History] tab: View the scaling execution history.
     • If you click [Details], you can view　detailed information for the selected history item.
   • [Notification settings] tab: Change notification events and notification recipients.
     • To add a new notification recipient, click [Manage notification recipients] and add the recipient (see Notification recipient addition guide).
   • [Server] tab: View the list and status of servers that belong to the group.
   • [Process management] tab: Check the status of processes and pause or restart them.

     Process	Description
     	LAUNCH (LANCH)
     	TERMINATE (TERMT)
     	HEALTH CHECK (HTHCK)
     	REPLACE UNHEALTHY (RPUNH)
     	SCHEDULED ACTIONS (SCACT)
     	ADD TO LOAD BALANCER (ADTLB)
     	ALARM NOTIFICATION (ALMNO)

Edit Auto Scaling Group information

To edit the details of a created Auto Scaling Group:

1. In the Classic environment of the NAVER Cloud Platform console, navigate to > Services > Compute > Auto Scaling.
2. Click the Auto Scaling Group menu.
3. Select an Auto Scaling Group and click [Edit].
4. Edit the details and click [OK].
   • For more information about each item, see 2. Configure group settings.

Delete Auto Scaling Group

To delete a created Auto Scaling Group:

1. In the Classic environment of the NAVER Cloud Platform console, navigate to > Services > Compute > Auto Scaling.
2. Click the Auto Scaling Group menu.
3. Click the Auto Scaling Group to delete and click [Delete].
4. When the delete popup window appears, click [OK].
   • The corresponding Auto Scaling Group disappears from the Auto Scaling Group list.