Available in VPC
You can create an Auto Scaling Group based on Launch Configurations.
Auto Scaling Group interface
The Auto Scaling Group interface includes the following components:

| Component | Description |
|---|---|
| ① Menu name | Displays the current menu name and the number of created items. |
| ② Basic features | Features displayed when you first access the Auto Scaling Group menu.
|
| ③ Post-creation features |
|
| ④ Auto Scaling Group list | Displays the list of created Auto Scaling Groups. |
View Auto Scaling Group list
You can view information for each created Auto Scaling Group. To view the Auto Scaling Group list:
If 1 or more Auto Scaling Groups have been created, the list is displayed. If there is no created Auto Scaling Group, the list is not displayed on the Auto Scaling Group interface.
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- 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.
- Hypervisor: The underlying hypervisor of the Auto Scaling server.
- 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.
- VPC: The name of the VPC in which the Auto Scaling Group is deployed.
- Subnet: The subnet mask and name of the subnet in which the Auto Scaling Group is deployed.
- Access Control Group: The name of the ACG applied to the Auto Scaling servers.
- Server configuration: The detailed specifications of the Auto Scaling servers.
- Default cooldown (seconds): The cooldown time applied when scaling is performed.
- My server image: The name of the custom server image used. If a default image is used, this field is left blank.
- Creation date: The date and time when the Auto Scaling Group was created.
- Health check grace period (seconds): The grace period applied to health checks.
- Target Group: The Target Group connected when a Load Balancer is connected.
- Detailed monitoring applied: Whether monitoring is applied to the servers created by the scaling policy.
Create Auto Scaling Group
To create an Auto Scaling Group in the NAVER Cloud Platform console:
You can create up to 100 Auto Scaling Groups per account and up to 30 servers per group.
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Click [Create Auto Scaling Group].
- When the Create Auto Scaling Group interface appears, complete the following steps in order:
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].
If no VPC and Subnet have been created in advance, you cannot configure the group. To create VPC and subnet, see VPC creation guide and Subnet creation guide.
- Auto Scaling Group name: Enter using 1 to 255 lowercase letters, numbers, and hyphens (-).
- VPC: Select the VPC in which to deploy the Auto Scaling Group.
- Subnet: Select the subnet 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.
- Detailed monitoring applied: Select whether to monitor the servers created by the scaling policy. If enabled, charges are applied according to the Cloud Insight pricing policy.
- 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.
- Health check type: The health check criteria for 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. Configure network access
Select the ACG to be applied to the Auto Scaling Group and click [Next].
If you do not have an ACG created in advance, create an ACG by referring to ACG creation guide.
4. 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.
5. 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.
- 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).
6. Review final settings
After reviewing the settings, click [Create Auto Scaling Group].
- The group is created and added to the Auto Scaling Group list.
To enable Auto Scaling policies based on monitoring events, the service must be integrated with Cloud Insight. For more information, see Monitoring event integration.
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.
Change Auto Scaling Group settings
You can change the policy, schedule, Launch Configuration, event notification, and detailed process of a created Auto Scaling Group. To change the settings:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Select an Auto Scaling Group and click [Settings].
- 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.
- [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).
- [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:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Select an Auto Scaling Group and click [Edit].
- Edit the details and click [OK].
- For more information about each item, see 2. Configure group settings.
View Auto Scaling Group execution history
To view the scaling execution history of an Auto Scaling Group:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Select an Auto Scaling Group and click [History].
- View the scaling execution history.
- You can view more detailed information by clicking a server in the list.
View servers in an Auto Scaling Group
To view the servers that belong to an Auto Scaling Group:
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Select an Auto Scaling Group and click [Server list].
- View the list of servers that belong to the group.
Delete Auto Scaling Group
To delete a created Auto Scaling Group:
If servers remain in the Auto Scaling Group, the group cannot be deleted. Adjust the minimum capacity or desired capacity so that no servers remain, and then try again.
- In the VPC environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Auto Scaling. - Click the Auto Scaling Group menu.
- Click the Auto Scaling Group to delete and click [Delete].
- When the delete popup appears, click [OK].
- The corresponding Auto Scaling Group disappears from the Auto Scaling Group list.