How-to guides

• 1: Launch Configuration
• 2: Manage Policy
• 3: Manage Schedule
• 4: Manage Notification

1 - Launch Configuration

To create an Auto-Scaling Group, a Launch Configuration must be created in advance.

Create Launch Configuration

You can create and use the Launch Configuration service in the Samsung Cloud Platform Console.

To create a Launch Configuration, follow these steps.

1. All Services > Compute > Virtual Server menu, please click. 1. Navigate to the Service Home page of the Virtual Server.

2. Click the Launch Configuration menu. 2. Go to the Launch Configuration List page.

3. On the Launch Configuration List page, click the Create Launch Configuration button. 3. Go to the Launch Configuration creation page.

4. On the Launch Configuration creation page, in the Image and version selection area, select the required information and click the Next button.

   Reference

   • Refer to the Virtual Server OS Image 제공 버전 for the images selectable in the Launch Configuration.
   • In Custom Image, you can select Image-Based and Snapshot-Based images.
     • Snapshot-Based type Image does not support future features such as distributed disk deployment, so for a stable Auto-Scaling configuration, we recommend using Image-Based type Image.
     • Image-Based type Image generation details can be found in Image-Based 유형의 Image 생성하기.

5. Enter the required information in the Service Information Input area of the Launch Configurationp creation page.

   Category	Required status	Detailed description
   Launch Configuration name	Essential	Launch Configuration name a name to distinguish the Launch Configuration
   Service Type > Server Type	Essential	Server type of Launch Configuration Standard: Standard specification commonly used High Capacity: Large‑capacity server specification above Standard Refer to Virtual Server 서버 타입 for selectable server types Since supported Availability Zones may differ by server type, verification is required via Support Center > Contact Us
   Block Storage	Required	Configure Block Storage according to the purpose of the Launch Configuration Basic OS: The area where the OS is installed and used Enter the size in Units; the minimum size varies depending on the OS Image type Alma Linux: Enter a value between 2 and 1,536 Oracle Linux: Enter a value between 5 and 1,536 RHEL: Enter a value between 2 and 1,536 Rocky Linux: Enter a value between 2 and 1,536 Ubuntu: Enter a value between 1 and 1,536 Windows: Enter a value between 4 and 1,536 SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Using the SSD_KMS disk type may result in performance degradation Additional: Use when extra space beyond the OS area is needed After selecting Use, enter the storage type and size Click the + button to add storage, or the x button to delete (up to 25 can be added) Enter the size in Units, with a value between 1 and 1,536 Since 1 Unit equals 8 GB, this creates 8 ~ 12,288 GB SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Using the SSD_KMS disk type may result in performance degradation SSD_MultiAttach: Volume that can be attached to more than one server For details on each Block Storage type, refer to Create Block Storage ___HTML_MARKER***
   Keypair	Essential	Select the user authentication method for the Launch Configuration Server authentication information for accessing the servers created by generating an Auto-Scaling Group with a Launch Configuration New creation: Create a new one if a new Keypair is needed Refer to Keypair 생성하기 for how to create a new Keypair Default login account list by OS Alma Linux: almalinux RHEL: cloud-user Rocky Linux: rocky Ubuntu: ubuntu Windows: sysadmin
   File Storage Settings	Selection	When performing Scale-out/Scale-in, you can configure File Storage to be automatically attached Volume: After clicking the Select button, choose the Volume to use in the File Storage selection popup You can select up to a maximum of 5 Only Volumes intended as source that can be attached to a Virtual Server can be selected High‑performance SSDs are disabled because they cannot be attached to a Virtual Server The selected Volume can be removed by clicking the X button

   Table. Launch Configuration service information input items

6. On the Launch Configuration Creation page, after entering information in the Additional Information Input area, click the Next button.

   Category	required status	Detailed description
   Init Script	Selection	The script that runs when a server in an Auto-Scaling Group using a Launch Configuration starts Enter within 45,000 bytes The Init Script must be a batch script for Windows, a shell script for Linux, or cloud‑init, depending on the selected image.
   tag	Selection	Add Tag Up to 50 per resource can be added Add Tag After clicking the Add Tag button, enter or select Key, Value values

   Table. Launch Configuration additional information entry fields

7. On the Check Creation Information page, verify the entered information and the estimated amount, then click the Create button.

   • When creation is complete, verify the created Launch Configuration on the Launch Configuration list page.

Launch Configuration View detailed information

The Launch Configuration service lets you view and edit the complete list of resources and their detailed information. On the Launch Configuration Details page, it consists of Detailed Information, Tags, Operation History tabs.

To view the detailed information of the Launch Configuration, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. Click the Launch Configuration menu. 2. Go to the Launch Configuration list page.
3. Launch Configuration List On the page, click the resource to view detailed information. 3. Launch Configuration Details Navigate to the page.
   • Launch Configuration Details At the top of the page, status information and additional feature information are displayed, and it consists of Details, Tags, Activity History tabs.

     Category	Detailed description
     Launch Configuration status	The status of the user-created Launch Configuration Active: available
     Delete Launch Configuration	Delete Launch Configuration button

     Table. Launch Configuration status information and additional features

Detailed Information

Launch Configuration List page allows you to view detailed information of the selected resource and, if necessary, modify the information.

Tag

On the Launch Configuration list page, you can view the tag information of the selected resource, and add, modify, or delete it.

Operation History

Launch Configuration List page allows you to view the operation history of the selected resource.

Launch Configuration Resource Management

Explains the resource management function of Launch Configuration.

Generate Image-Based type Image

To create an Image of the Image-Based type, follow the steps below.

To create an Image of the Image-Based type, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
3. On the Image List page, click the Image to create an Image of the Image-Based type. 3. Image Details go to the page.
4. Create Image for Sharing button, click it. 4. A popup window opens to notify the creation of a shared Image. 4. The popup’s ‘Share to another Account’ content will not be processed. 4. If you only proceed with ‘Create Image for sharing’, an Image-Based type Image will be generated.
5. After reviewing the contents of the popup window, click the Confirm button.

Delete Launch Configuration

Deleting unused Launch Configurations can reduce operating costs. However, terminating the Launch Configuration may cause the running service to stop immediately, so you should proceed with the termination only after fully considering the impact of service interruption.

To delete a Launch Configuration, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. Click the Launch Configuration menu. 2. Go to the Launch Configuration List page.
3. Launch Configuration List On the page, click the resource to be terminated. 3. Navigate to the Launch Configuration Details page.
4. Click the Delete Launch Configuration button.
5. After the deletion is complete, verify on the Launch Configuration list page that the resource has been deleted.

2 - Manage Policy

You can dynamically adjust the number of servers in an Auto-Scaling Group based on monitoring metrics. When the metric exceeds the threshold you set, the server count is adjusted. At that time, you can choose one of three methods to adjust the server count: increase or decrease by a specified number, increase or decrease by a specified percentage, or fix the server count to a given value. When servers are launched or terminated due to a policy, the monitoring metric, such as CPU utilization, may temporarily exceed the threshold registered in the policy. However, because this is a brief moment, a cooldown period is set to avoid treating it as an abnormal condition. You can add and manage policies for an Auto-Scaling Group created in the Samsung Cloud Platform Console.

Add Policy

You can add policies to an Auto-Scaling Group. To add a policy to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.

3. Auto-Scaling Group List page, click the resource you want to view detailed information for. You will be taken to the Auto-Scaling Group Details page.

4. Click the Policy Tab. You will be taken to the Policy Tab page.

5. Click the Add Policy button. The Add Policy popup window opens.

   Category	Required	Detailed description
   Category	Required	Policy Category Scale In: return server count Scale Out: increase server count
   Policy Name	Required	Name for policy-specific categorization
   Execution conditions	Required	Conditions to execute the policy Statistic: How to calculate the Metric Type Average: Average of servers in the Auto-Scaling Group Min: Minimum value among servers in the Auto-Scaling Group Max: Maximum value among servers in the Auto-Scaling Group Metric Type: CPU Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets) Operator: >= > <= < Threshold: Threshold corresponding to the Metric Type Period: Continuous duration required to trigger the condition (the condition must be continuously satisfied for N minutes for the policy to execute)
   execution unit	Required	Policy execution method Policy Type: Select the type of policy to execute. Increase or decrease the number of servers by a specified count: Increase or decrease the server count to the Target Value Increase or decrease the number of servers by a specified ratio: Increase or decrease by the Target Value ratio Fix the number of servers to the entered value: Fix the server count according to the Target Value Target Value: The number or ratio to apply for the selected Policy Type
   cooldown	Required	The waiting time (seconds) when a server is started or terminated due to a policy The default is 300 seconds, and it can be set between a minimum of 60 seconds and a maximum of 3,600 seconds.

   Table. Add Policy Popup Items
   Reference

   Policy > Cooldown Settings

   • When a server is started or terminated due to a policy, it waits for the configured cooldown period. Temporarily, the monitoring metric CPU utilization may exceed the threshold defined in the policy. However, because this is a transient moment rather than a condition for adjusting the number of servers, it is not considered an abnormal situation, and the system waits by applying the cooldown time.
   guide

   Policy execution operates within the configured Min/Max server count range.

   • Even if you input values outside the Min/Max server count range—such as increasing, returning, or fixing the number of servers—it operates within the configured Min/Max server count.
   • Example: When the minimum number of servers is 3, even if you set the server count fixed to 1, the server count does not drop to 1 and remains at the minimum of 3.

6. Add Policy After entering the required values in the popup window, click the Confirm button. The added policy can be viewed in the Policy List.

Policy creation example

The following is an explanation of the policy example. Please refer to it when creating a policy.

Edit Policy

You can modify the policies of an Auto-Scaling Group. To modify the policies of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.

3. Auto-Scaling Group List page, click the resource to view detailed information. You will be taken to the Auto-Scaling Group Details page.

4. Click the Policy Tab. You will be taken to the Policy Tab page.

5. Click the More > Edit button for the policy you want to modify. The Policy Edit Popup opens.

   Category	Required	Detailed description
   Category	Required	Policy Classification Scale In: Return server count Scale Out: Increase server count
   Policy Name	Required	Name for policy-specific categorization
   Execution conditions	Required	Conditions to execute the policy Statistic: Method to calculate the Metric Type Average: Average of servers in the Auto-Scaling Group Min: Minimum value among servers in the Auto-Scaling Group Max: Maximum value among servers in the Auto-Scaling Group Metric Type: CPU Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets) Operator: >= > <= < Threshold: Threshold corresponding to the Metric Type Period: Continuous duration (in minutes) that triggers the execution condition
   execution unit	Required	Policy execution method Policy Type: Select the type of policy to execute. Increase or decrease the number of servers by a specified count: Increase or reduce the server count to the Target Value Increase or decrease the number of servers by a specified ratio: Increase or reduce by the Target Value ratio Fix the number of servers to the entered value: Fix the server count according to the Target Value Target Value: The number or ratio to execute the selected Policy Type
   Cool down	Required	The waiting time (seconds) when a server is started or terminated due to a policy The default is 300 seconds, and it can be set from a minimum of 1 second up to a maximum of 3,600 seconds

   Table. Policy edit popup items

6. Edit Policy In the popup window, after entering the required values, click the Confirm button.

Policy addition and modification constraints

When adding or modifying a policy, constraints exist based on the policy classification, execution conditions, and the scope of those conditions. Below is an example of constraints for the policy. Refer to the constraint examples to add or modify the policy.

Example 1 - Need to check for duplicate registration of policy classification/execution conditions

Policy classification (Scale Out or Scale In) and execution condition (Metric type) cannot be registered redundantly with the same values.

If a policy is registered as above, you cannot add a policy with the category (Scale Out) execution condition (Metric type=CPU Usage) or modify it to that condition.

Example 2 - Need to verify the execution condition range for execution conditions (Metric type) and execution conditions (Statistic) according to policy classification

When the policy type (Scale Out or Scale In) differs, duplicate registration of the execution condition range (Comparison operator + Threshold) is not allowed for the same execution condition (Metric type) and execution condition (Statistic).

If a policy is registered as shown above, you cannot add a policy as below or modify it under the following conditions.
If the average CPU Usage is 60% or higher, a Scale Out policy is already registered; therefore, registering a Scale In policy when the average CPU Usage is 60% or lower would duplicate the 60% execution condition and cannot be added.

Example 3 - Need to verify the execution condition range for execution conditions (Metric type) and execution conditions (Statistic) according to policy classification

When the policy classification (Scale Out or Scale In) differs, duplicate registration of the execution condition range (Comparison operator + Threshold) is not allowed for the same execution condition (Metric type) and execution condition (Statistic).

If a policy is registered as shown above, you cannot add a policy as below or modify it under the following conditions.
When the average CPU Usage is 10% or less, a Scale In policy is already registered; therefore, if the average CPU Usage is less than 60% / 60% or less / 10% or more / exceeds 9%, you cannot register a Scale Out policy because the execution condition ranges would overlap.

Example 4 - Execution conditions (Metric type) and execution conditions (Statistic) can be registered according to the execution condition range based on policy classification

If the policy type (Scale Out or Scale In) differs, you can register when the execution condition (Metric type) is the same but the execution condition (Statistic) is different, or when the execution condition range (Comparison operator + Threshold) does not overlap.

If a policy is already registered as shown above, you can add a policy as below or modify it with the following conditions. Registration is possible when the execution condition ranges do not overlap, or when the execution condition (Statistic) differs.

Delete Policy

You can delete a policy of an Auto-Scaling Group. To delete a policy of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. Auto-Scaling Group List page: click the resource you want to view details for. You will be taken to the Auto-Scaling Group Details page.
4. Click the Policy Tab. You will be taken to the Policy Tab page.
5. Select the policy to delete and click the Delete button. The Policy Deletion Confirmation popup opens.
6. Policy Deletion Confirmation Check the popup window and click the Confirm button.

3 - Manage Schedule

You can schedule reservations daily, weekly, monthly, or one-time, and set the desired number of servers at the specified time. This is useful when you can predict when you need to decrease or increase the number of servers.

Add schedule

You can add a schedule to an Auto-Scaling Group. To add a schedule to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. Auto-Scaling Group List page, click the resource you want to view detailed information for. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Click the Add Schedule button. The Add Schedule popup window opens.

   Category	required	Detailed description
   Schedule name	Required	Name to distinguish by schedule
   Select server count	Required	Select the number of servers to adjust when executing the schedule Min: The minimum number of servers the Auto-Scailg Group should maintain Desired: The target number of servers within the Auto-Scailg Group Max: The maximum number of servers the Auto-Scailg Group can maintain
   Enter the number of servers	Required	Enter the value for the selected number of servers Min value: Enter a value between 0 and 50. (Min≤Desired≤Max) Desired value: Enter a value between 0 and 50. (Min≤Desired≤Max) Max value: Enter a value between 0 and 50. (Min≤Desired≤Max)
   Period	Required	Schedule execution frequency Daily: You can set the Start date, End date, and Permanent options for a daily schedule. You can also set the Time and Time zone Weekly: You can set the Start date, End date, Permanent options, and the Time and Time zone. You can also select the Day of week on which the weekly schedule will run. Monthly: You can set the Start date, End date, Permanent options, and the Time and Time zone. You can also enter the Date on which the monthly schedule will run One-time: You can set the Time and Time zone. You can also set the Date on which the one-time schedule will run
   Start date	Selection	Set schedule start date Cannot set a date earlier than the current date. The default is the current date.
   End date	Selection	Set schedule end date Cannot set a date earlier than the current date. The default is the current date plus 7 days.
   permanent	Selection	When configuring permanently, set the schedule end date to 9999-12-31
   time	Required	Schedule execution time setting Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
   time zone	Required	Schedule execution time zone (example: Asia/Seoul (GMT +09:00))
   day of the week	Required	When Period is set to Weekly, select the Day of the week to execute the schedule
   Date	Required	When Period is set to Monthly, enter the Date on which the schedule will run Enter one or more values from -31 to 31, excluding 0. (Example: 3,4,5) When Period is set to Once, set the Date on which the schedule will run Setting a date earlier than the current date is not allowed. The default is the current date.

   Table. Schedule addition popup items
6. Add Schedule After entering the required values in the popup window, click the Confirm button.
7. Add Schedule Confirmation After checking the message in the popup window, click the Confirm button.

Modify schedule

You can modify the schedule of an Auto-Scaling Group. To modify the schedule of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource for which you want to view detailed information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Click the More > Edit button of the schedule you want to modify. The Edit Schedule popup window will open.

   Category	required	Detailed description
   Schedule name	Required	Name to distinguish by schedule
   Select number of servers	Required	Select the number of servers to adjust when executing the schedule Min: The minimum number of servers the Auto-Scailg Group should maintain Desired: The target number of servers within the Auto-Scailg Group Max: The maximum number of servers the Auto-Scailg Group can maintain
   Enter number of servers	Required	Enter the value for the selected number of servers Min value: Enter a value between 0 and 50. (Min≤Desired≤Max) Desired value: Enter a value between 0 and 50. (Min≤Desired≤Max) Max value: Enter a value between 0 and 50. (Min≤Desired≤Max)
   period	Required	Schedule execution frequency Daily: You can set the Start Date and End Date, and Permanent setting for the daily schedule. You can also set the Time and Time Zone Weekly: You can set the Start Date and End Date, Permanent setting, and the Time and Time Zone. You can also select the Day of Week for the Weekly schedule to run. Monthly: You can set the Start Date and End Date, Permanent setting, and the Time and Time Zone. You can also enter the Date for the Monthly schedule to run. Once: You can set the Time and Time Zone. You can also set the Date for the Once schedule to run
   Start date	Selection	Set schedule start date Cannot set a date earlier than the current date. The default is the current date.
   End date	Selection	Set schedule end date Cannot set a date earlier than the current date. The default is the current date plus 7 days.
   Permanent	Selection	When configuring permanently, set the schedule end date to 9999-12-31.
   time	Required	Schedule execution time setting Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
   time zone	Required	Schedule execution time zone (example: Asia/Seoul (GMT +09:00))
   day of the week	Required	When Period is weekly, select the day of the week to run the schedule.
   Date	Required	When Period is set to Monthly, enter the Date on which the schedule will run Enter one or more values from -31 to 31, excluding 0. (Example: 3,4,5) When Period is set to Once, set the Date on which the schedule will run Cannot set a date earlier than the current date. The default is the current date.

   Table. Schedule edit popup items
6. Schedule Edit After entering the required values in the popup window, click the Confirm button.
7. Schedule Modification Confirmation After checking the message in the popup window, click the Confirm button.

Delete schedule

You can delete the schedule of an Auto-Scaling Group. To delete the schedule of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource for which you want to view detailed information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Select the schedule to delete and click the Delete button. Schedule Deletion Confirmation popup will open.
6. Schedule Deletion Confirmation Check the popup window and click the Confirm button.

4 - Manage Notification

You can designate a notification recipient and send alert messages via E‑mail or SMS for specific situations.

Add notification

You can add notifications to an Auto-Scaling Group. To add notifications to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to which you want to add notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. Click the Add Notification button. The Add Notification popup opens.
6. Add Notification After entering the required values in the popup window, click the Confirm button.

   Category	Detailed description
   Notification timing	Notification timing when an Auto-Scaling Group alert occurs Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met Multiple selection allowed
   Notification recipient	User who will receive the notification when an alert occurs Click the Add Notification Recipient button to select a user Only Samsung Cloud Platform users can be selected as recipients

   Table. Notification items

7. Add Notification Confirmation After checking the message in the popup window, click the Confirm button.

Edit Notification

You can modify the notification settings of an Auto-Scaling Group. To modify the notification settings of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to edit the notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. In the notification list, click the More > Edit button for the notification you want to modify. The Edit Notification popup window will open.
6. Edit Notification After editing the notification information in the popup window, click the Confirm button.

   Category	Detailed description
   Notification timing	Notification timing when an Auto-Scaling Group alert occurs Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met Multiple selection allowed

   Table. Notification edit items
7. Edit Notification Confirmation After checking the message in the popup window, click the Confirm button.

Delete Notification

You can delete notifications for an Auto-Scaling Group. To delete notifications for an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to edit the notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. In the notification list, select the notification you want to delete, then click the Delete button. The Delete Notification Confirmation popup will open.
6. Delete Notification Confirmation Review the popup window and click the Confirm button.