This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

How-to guides

Users can create the service by entering the required information for an Auto-Scaling Group and selecting detailed options through the Samsung Cloud Platform Console.

Create Auto-Scaling Group

You can create and use the Auto-Scaling Group service from the Samsung Cloud Platform Console.

Reference
To create an Auto-Scaling Group, you need to create a Launch Configuration in advance. Please refer to Create Launch Configuration.

To create 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 Create Auto-Scaling Group button. You will be taken to the Create Auto-Scaling Group page.

  4. On the Auto-Scaling Group Creation page, enter the information required to create the service.

    • In the Launch Configuration area, select the Launch Configuration.
      • Launch Configuration creation button can be clicked to create a new Launch Configuration.
    • Enter or select the required information in the Service Information Input area.
      Category
      Whether required
      Detailed description
      Auto-Scaling Group nameRequiredAuto-Scaling Group name
      • Manage servers of the same type and purpose as a group
      Server nameRequiredServer name to be created within the Auto-Scaling Group
      • The server name is automatically assigned as a combination of the entered server name and a sequence, serving as an identifier to distinguish servers created within the Auto-Scaling Group.
      Number of serversRequiredNumber of servers to create in the Auto-Scaling Group
      • Enter a value between 0 and 20 (Min≤Desired≤Max)
      • Min: Set the minimum number of servers the Auto-Scaling Group should maintain
      • Desired: Set the target number of servers within the Auto-Scaling Group; also indicates the number of servers initially created when the Auto-Scaling Group is created
      • Max: Set the maximum number of servers the Auto-Scaling Group can maintain
      • After creating the Auto-Scaling Group, you can adjust the settings using the Edit button. For details, see Modify Server Count
      Desired server count manual settingSelectionSelect whether to manually change the Desired number of servers
      Network Settings > Network SettingsRequiredNetwork settings for Auto-Scaling Group
      • Select the desired VPC and standard Subnet
      • IP can only be auto-generated.
      • When you select local Subnet, you can choose the desired local Subnet, and IP can only be auto-generated
      Network Settings > Security GroupSelectionTo allow required connections, you need to configure a Security Group
      • If you do not configure a Security Group, all inbound and outbound traffic will be blocked according to the default rule (Any/Deny)
      • For Linux servers, allow SSH traffic
      • For Windows servers, allow RDP traffic
      • Even after creating an Auto-Scaling Group, configure it using the modify button. For details, refer to Configure Security Group
      Load BalancerSelectionConnect the Auto-Scaling Group to a Load Balancer
      • Register the Auto-Scaling Group’s servers as members of the LB server group
      • LB server group: Select a LB server group that exists in the chosen VPC
      • Port: Enter a value between 1 and 65,534
      • Press the + button to add an LB server group (up to a total of three LB server groups and ports are allowed)
      • LB server groups that use Weighted Round Robin or Weighted Least Connection load balancing cannot be selected
      • Draining Timeout value: After checking Draining Timeout as Enabled, you can set the Draining Timeout value
        • Draining Timeout: The waiting period before removing a server from the Load Balancer
          • Since sessions may remain connected to the server, setting a Draining Timeout and waiting allows safe session termination
        • If the Load Balancer is unused, Draining Timeout cannot be set
        • The default is 300 seconds; you can enter a value from 1 second up to 3,600 seconds.
      Table. Auto-Scaling Group service information input items
    • In the Scaling policy setting area, set the scaling policy.
      • For detailed information on policy settings, refer to Add Policy.
        Category
        Required
        Detailed description
        Current settingSelectionSet scaling policy now
        • Add Policy button click shows policy information input fields
        Set laterSelectionAfter creating an Auto-Scaling Group, set policies on the detail information page
        Table. Auto-Scaling Group scaling policy configuration items
    • In the Notification Settings area, configure the notification recipients and notification method.
      • For detailed information on notification settings, see Add Notification.
        Category
        Required?
        Detailed description
        Current settingSelectionSet the notification recipients and notification method now
        • Click the Add Notification button to open the Add Notification popup
        • For detailed information about notification settings, see the details
        • In the notification recipients list, click the Edit button to modify the notification information
        Set laterSelectionAfter creating an Auto-Scaling Group, set the notification recipients and notification method on the details page.
        Table. Auto-Scaling Group notification configuration items
    • In the Additional Information Input area, enter or select the required information.
      Category
      Required status
      Detailed description
      Status checkSelectionCheck the status of Virtual Server and Load Balancer and replace servers that are Unhealthy
      • Virtual Server status check: Enabled is the default and cannot be changed
      • Load Balancer status check: Enabled only when a Load Balancer is connected in the service information input area
      • Grace period: Set the time to defer status checks until the newly added server operates normally
        • Enter 0 to disable the status check grace period
      tagSelectionAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. Auto-Scaling Group additional information input fields
      Caution
      A server that the user changes to Stop is not considered Unhealthy, so even when using the health check feature, the server will not be replaced.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.

    • When creation is complete, check the created Auto-Scaling Group on the Auto-Scaling Group list page.

Check detailed information of Auto-Scaling Group

Auto-Scaling Group service allows you to view and edit the full resource list and detailed information. The Auto-Scaling Group Details page is composed of Details, Policies, Schedule, Virtual Server, Load Balancer, Tags, Operation History tabs.

To view detailed information about the 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 view detailed information. You will be taken to the Auto-Scaling Group Details page.
    • Auto-Scaling Group Details page displays status information and additional feature information, and consists of Details, Policies, Schedule, Virtual Server, Load Balancer, Tags, Activity History tabs.
      CategoryDetailed description
      Auto-Scaling Group statusStatus of the Auto-Scaling Group created by the user
      • Creating: Creating Auto-Scaling Group
      • In Service: Serviceable state
      • Scale In: Scale In in progress
      • Scale Out: Scale Out in progress
      • Cool Down: Cooling down
      • Terminating: Terminating Auto-Scaling Group
      • Attach to LB: Attaching to Load Balancer
      • Detach from LB: Detaching from Load Balancer
      Delete Auto-Scaling GroupButton to delete Auto-Scaling Group
      Table. Auto-Scaling Group status information and additional features

Detailed Information

Auto-Scaling Group List page lets you view detailed information of the selected resource and modify it if necessary.

CategoryDetailed description
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Auto-Scaling Group, it refers to the Auto-Scaling Group SRN
Resource nameResource name
  • In Auto-Scaling Group, it refers to the Auto-Scaling Group name
Resource IDUnique resource ID in the service
constructorUser who created the service
Creation date and timeService creation date and time
editorUser who edited the service information
Modification dateDate and time the service information was modified
Auto-Scaling Group nameAuto-Scaling Group name
Launch Configuration nameWhen creating an Auto-Scaling Group, the selected Launch Configuration name
  • the image template used when the Auto-Scaling Group creates a Virtual Server
Number of serversCurrent number of instances in the Auto-Scaling Group and the configured Min, Desired, Max instance counts
Manually set the desired number of serversDesired server count manual setting enable/disable
VPCVPC information of the Auto-Scaling Group
General SubnetGeneral Subnet and NAT IP usage information for the Auto-Scaling Group
Local SubnetLocal Subnet of Auto-Scaling Group
Security GroupAuto-Scaling Group’s Security Group
Status checkWhether to use the replacement function for Virtual Server and Load Balancer in Unhealthy state
  • Virtual Server: Enabled is the default and cannot be changed
  • Load Balancer: Indicates usage when a Load Balancer is attached
    • Enabled*: When a Load Balancer is connected and health check is used
    • Disabled: When a Load Balancer is connected and health check is not used
    • Enabled (does not operate because no LB is currently connected): When a Load Balancer is connected and health check is enabled, but the Load Balancer has been detached
    • -: When no Load Balancer is connected
  • Grace period: Time to defer health checks
    • If set to 0, the health check grace period is not used
  • Edit button can be clicked to set the Load Balancer health check usage and Grace period. For details, see 상태 체크 변경하기
Table. Auto-Scaling Group Details – Details Tab Items
Caution
A server that the user changes to Stop is not considered Unhealthy, so even when using the health check feature, the server will not be replaced.

Policy

On the Auto-Scaling Group List page, you can view the policy list of the selected resource and, if needed, add or manage policies.

CategoryDetailed description
CategoryPolicy Type
  • Scale In: return servers
  • Scale Out: increase server count
Policy NameName for policy-specific categorization
Execution conditionsConditions to trigger 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, Memory 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 unitMethod of executing the policy
  • Policy Type: Select the type of policy to execute
    • Increase or decrease the number of servers by a specified count: Increase or return the server count to Target Value
    • Increase or decrease the number of servers by a specified ratio: Increase or return 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 the selected Policy Type
Cool downThe 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
More > EditModify the policy information
More > EnableEnable this policy
  • Selectable only when the policy is disabled
More > DisableDisable the policy
  • Can be selected only when the policy is active
Table. Auto-Scaling Group Details - Policy Tab Items
Reference
For policy management and policy example explanations, please refer to Policy Management.

Schedule

On the Auto-Scaling Group List page, you can view the schedule list of the selected resource and, if necessary, add or manage schedules.

CategoryDetailed description
NameSchedule name
MinMinimum number of servers set in the schedule
DesiredNumber of target servers set in the schedule
MaxMaximum number of servers set in the schedule
periodSchedule execution frequency
  • Set to one of daily/weekly/monthly/once
Date/Day of WeekSchedule execution date or day of week
  • Date/day selected according to the schedule interval
Execution timeSchedule execution time
time zoneSchedule execution time window
statusSchedule status
More > EditEdit the schedule information
More > ActivateActivate this schedule
  • Can be selected only when the schedule is disabled
More > DisableDeactivate this schedule
  • Can be selected only when the schedule is active
Add scheduleAdd a new schedule
DeleteDelete the selected schedule from the list
Table. Auto-Scaling Group Details – Schedule Tab Items

Reference
For detailed information about schedule management, see Schedule Management.

Virtual Server

Auto-Scaling Group List You can view the Virtual Server list of the selected resource on the page.

CategoryDetailed description
Server nameIf you click the Server Name of the server created in the Auto-Scaling Group
  • , you will be taken to the Virtual Server Details page
IPIP assigned to the server
Creation date and timeThe date and time the server was created
statusResult of status check for Virtual Server and Load Balancer
  • Healthy: When both Virtual Server and Load Balancer are in Healthy state
  • Unhealthy: When one or more of Virtual Server or Load Balancer are in Unhealthy state
    • Unhealthy: Including cases where one or more of the three Load Balancer server groups connected to the Virtual Server are Unhealthy
    • The cause of Unhealthy can be identified in the Work History tab
Table. Auto-Scaling Group Details - Virtual Server Tab Items

Load Balancer

On the Auto-Scaling Group List page, you can view the Load Balancer list of the selected resource, and, if needed, add or manage Load Balancers.

CategoryDetailed description
Draining TimeoutDraining Timeout usage
  • When you click the Edit button, set the Draining Timeout usage
  • If it is already in use, change the time
  • If the Load Balancer is not in use, Draining Timeout cannot be configured.
Load BalancerLoad Balancer usage
  • Edit button sets the Load Balancer usage
  • If already in use, add or change the Load Balancer
  • Up to three LB server groups can be added
Load Balancer > Load Balancer nameLoad Balancer name to attach to the Auto-Scaling Group
Load Balancer > LB server groupLB server group of the Load Balancer
  • LB server groups that use Weighted Round Robin or Weighted Least Connection load balancing cannot be selected
Load Balancer > PortPort registered as a member in the LB server group
Table. Auto-Scaling Group Details - Load Balancer tab items
Reference

Notification

Auto-Scaling Group List page allows you to view the notification recipients and notification methods for the selected resource.

CategoryDetailed description
Notification recipientName of the notification recipient
emailNotification recipient’s email
Create serverWhether to send notifications when a server creation-related alert occurs
  • On success: Whether to send when creation succeeds
  • On failure: Send when creation fails
Server terminationWhether to send a notification when a server termination-related alert occurs
  • Success: Whether to send when termination succeeds
  • Failure: Send when termination fails
When the policy execution condition is satisfiedWhether to generate a notification when the policy execution condition is satisfied
statusNotification activation status
  • Active: Enabled
More > EditEdit the notification information
Show more > EnableEnable this notification information
  • Selectable only when the notification is disabled
More > DisableDisable this notification information
  • Selectable only when the notification is active
Add notificationAdd a new notification
DeleteDelete the selected notification from the list
Table. Auto-Scaling Group Details - Notification Tab Items
Reference
For details on notification settings, refer to Manage Notifications.

tag

Auto-Scaling Group List page lets you view the tag information of selected resources, and add, modify, or delete them.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Auto-Scaling Group Details - Tag Tab Items

Work History

You can view the operation history of the selected resource on the Auto-Scaling Group List page.

CategoryDetailed description
Task History ListResource Change History
  • Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Check operator information
Table. Auto-Scaling Group Details - Task History Tab Items

Auto-Scaling Group Managing Resources

If you need to manage a created Auto-Scaling Group, you can perform actions on the Auto-Scaling Group Details page.

Edit Launch Configuration

You can modify the Launch Configuration of an Auto-Scaling Group.

Reference
Even if you modify the Launch Configuration, it will not affect servers that are already part of the Auto-Scaling Group; the changes will only apply to servers created thereafter. To apply the updated Launch Configuration to all servers in the Auto-Scaling Group, set the server count (Desired) to 0 to delete the existing servers, then adjust the server count (Desired) to the desired quantity.

To modify the Launch Configuration 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 you want to edit the Launch Configuration for. You will be taken to the Auto-Scaling Group Details page.

  4. Launch Configuration name. Click the Edit button. The Launch Configuration Edit popup opens. You can view the list of selectable Launch Configurations.

    Category
    Detailed description
    Launch Configuration nameLaunch Configuration name
    imageLaunch Configuration OS Image
    Server typeLaunch Configuration server type
    Block StorageLaunch Configuration Block Storage Settings
    Number of Auto-Scaling GroupsNumber of Auto-Scailg Groups with Launch Configuration applied
    View DetailsButton to view Launch Configuration details
    Table. Launch Configuration list items

  5. In the Launch Configuration Edit popup, select the Launch Configuration to modify, then click the Confirm button. The Launch Configuration Edit Notification popup opens. Check the message in the Launch Configuration Edit Notification popup and click the Confirm button.

Edit server count

You can modify the number of servers in the Auto-Scaling Group.

Reference
The maximum configurable number of servers is 50. However, when a Load Balancer is present, servers not connected to the Load Balancer are excluded.

To modify the number of servers in 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 server count. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Edit button for server count. The Edit Server Count popup opens.
  5. Modify Server Count In the popup window, after entering the required fields, click the Confirm button.
    Category
    Required
    Detailed description
    Number of servers > MinRequiredMinimum number of servers to modify
    • Set the number of servers that the Auto-Scaling Group should maintain at a minimum
    Number of servers > DesiredRequiredTarget server count to modify
    • Set the target server count within the Auto-Scaling Group
    Number of servers > MaxRequiredTarget number of servers to modify
    • Set the maximum number of servers the Auto-Scailg Group can maintain
    Table. Auto-Scailg Group server count modification items

Terminate Virtual Server Created by Auto-Scaling Group

Virtual Servers created in an Auto-Scaling Group can be terminated by clicking the terminate button on the Virtual Server’s detail page or by modifying the server count.

Warning
  • Be careful, as data cannot be recovered after terminating the service.
  • To cancel the service, first disconnect the File Storage and disable the Lock. If the File Storage is connected or a Lock is set, you cannot cancel the Virtual Server.
Reference
  • If you terminate a Virtual Server created in an Auto-Scaling Group, the associated Load Balancer is automatically detached.
  • When a Virtual Server is terminated, the status of the attached Storage is as follows.
    • If Delete on termination is not set: the volume will not be deleted even if the Virtual Server is terminated.
    • When Delete on termination is set: terminating the Virtual Server deletes the volume. However, if a Snapshot exists, the volume is not deleted even when Delete on termination is set.
    • Multi attach volume: It can be deleted only when the server you are deleting is the last remaining server attached to the volume.

Cancel on the Virtual Server detail page

To cancel a Virtual Server on the Virtual Server detail page, follow these steps.

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
  3. On the Virtual Server List page, select the Virtual Server created by the Auto-Scaling Group. Navigate to the Virtual Server Details page.
  4. Click the Cancel Service button on the Virtual Server Details page. A popup confirming the server termination will appear.
  5. Click the Confirm button. Server termination is complete.

Cancel by adjusting the server count

To cancel a Virtual Server by modifying the server count, follow the steps below.

  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 terminate the Virtual Server. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Edit button of the Server Count item. The Server Count Edit popup opens.
  5. Server Count Edit In the popup window, after reducing the Desired number, click the Confirm button. As the Desired server count is adjusted, the Virtual Server will be terminated.
Notice
  • If Desired server count manual setting is set to unused, you cannot modify the Desired server count. To modify the Desired server count, see Desired server count manual setting modification.
  • When a Virtual Server is terminated, the Desired server count remains unchanged, and scale‑out proceeds according to the Desired check batch.

Modify manual setting of desired server count

You can manually change the Desired server count of the Auto-Scaling Group.

Reference
Desired server count manual setting use not selected, you cannot modify the Desired server count in the server count edit of the details. Desired server count is automatically adjusted by checking the Virtual Server status every 10 minutes.

To modify the manual setting of the Desired server count 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 manually change the Desired server count. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Edit button for the server count. The Desired server count manual setting popup opens.
  5. Desired server count manual setting After selecting whether to use it in the popup window, click the Confirm button.

Configure Security Group

You can configure the Security Group of an Auto-Scaling Group.

Reference
Even if you modify the Security Group, the change does not apply to servers already created in the Auto-Scaling Group; it only takes effect for servers created thereafter. To apply the updated Security Group to all servers in the Auto-Scaling Group, set the server count (Desired) to 0 to delete all existing servers, then adjust the server count (Desired) to the desired quantity.

Follow these steps to configure the Security Group of an Auto-Scaling Group.

  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 configure the Security Group. You will be taken to the Auto-Scaling Group Details page.

  4. Click the Edit button for Security Group. Security Group Edit popup opens. You can view the list of selectable Security Groups.

    CategoryDetailed description
    Security Group nameSecurity Group name
    Table. Security Group list items

  5. Security Group edit In the popup window, after selecting the Security Group, click the Confirm button. Security Group edit notification popup opens. Check the message of the Security Group edit notification popup and click the Confirm button.

Change status check

You can configure it to check the status of Virtual Server and Load Balancer and automatically replace servers that are in an Unhealthy state.

Caution
  • The Load Balancer status check feature can only be used when a Load Balancer is in use.
  • A server that the user changes to Stop is not considered Unhealthy, so even if you use the health check feature, the server will not be replaced.
To change whether the Load Balancer health check feature of an Auto-Scaling Group is enabled, follow the steps below.

  1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
  2. Click the Auto-Scaling Group menu. Go to the Auto-Scaling Group list page.
  3. On the Auto-Scaling Group List page, click the resource for which you want to change the Load Balancer health check function. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Edit button of Status Check. Status Check Edit popup window opens.
  5. Status Check Edit In the popup, choose whether to enable Load Balancer Status Check.
  6. After entering the Grace period, click the Confirm button.
    • If you do not want to use the grace period, set the grace period to 0.

Manage Additional Information for Auto-Scaling Group

You can set the Load Balancer of an Auto-Scaling Group to enabled and select the LB server group. For an Auto-Scaling Group that is using a Load Balancer, you can change it to disabled.

Modify Load Balancer Draining Timeout

You can set the Load Balancer Draining Timeout of an Auto-Scaling Group.

Reference

The Draining Timeout is the time to wait before detaching a server from the Load Balancer.

  • Because sessions may remain connected to the server, setting a Draining Timeout and waiting allows you to clean up sessions more safely.
  • If the Load Balancer is unused, Draining Timeout cannot be set.
  • The default is 300 seconds, and it can be set from a minimum of 1 second up to a maximum of 3,600 seconds.

To set the Load Balancer Draining Timeout 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. Auto-Scaling Group List page, click the resource to set the Load Balancer Draining Timeout. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
  5. Click the Edit button for Draining Timeout. The Draining Timeout Edit popup opens.
  6. Draining Timeout Edit In the popup window, select whether to use Draining Timeout, and enter the Draining Timeout duration (seconds).
  7. Draining Timeout Edit After verifying the input values in the popup window, click the Confirm button. Draining Timeout Edit Notification popup window opens. Check the message in the notification popup and click the Confirm button.

Using Load Balancer

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

Reference
  • When a server in the Auto-Scaling Group is created, it is automatically added as a member of the selected Load Balancer’s LB server group, and when the server is terminated, it is removed from the LB server group’s members.
  • If Draining Timeout is used, after waiting for the Draining Timeout (seconds), the server is removed from the LB server group’s members.
  • When a Member is separated due to Load Balancer modification, it waits in the Detach from LB state; when a Member is separated due to Scale In, it waits in the Scale In state.
  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 that will use the Load Balancer. Navigate to the Auto-Scaling Group Details page.
  4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
  5. Click the Edit button of the Load Balancer. The Load Balancer Edit popup opens.
  6. Load Balancer Edit Please select whether to use it in the popup. Selecting Use allows you to choose a Load Balancer.
    CategoryDetailed description
    LB server groupLB server group name
    • Select the LB server group that is created in the selected VPC
    • LB server groups that use Weighted Round Robin or Weighted Least Connection load balancing cannot be selected
    PortPort information of the LB server group
    • When registering as a member of the LB server group, enter the required port information in the registration details.
    • Enter a value between 1 and 65,534
    Table. Load Balancer list items
    • Click the + button to add an LB server group. Up to three are allowed. Click the X button to remove the added Load Balancer.
  7. Check the Load Balancer list and click the Confirm button. Load Balancer Modification Notification popup opens. Verify the message in the notification popup and click the Confirm button.
Caution
  • Please be careful, as separating or connecting servers from the Load Balancer may affect the service.
  • If Draining Timeout is in use, setting the Load Balancer to unused or removing some of the attached Load Balancers with the X button will not detach immediately. After waiting for the Draining Timeout (seconds), the server is detached from the Load Balancer. At that time, the Auto-Scaling Group remains in the Detach from LB state.
Reference

Not Using Load Balancer

You can modify the Auto-Scaling Group’s Load Balancer to be unused. To set the Auto-Scaling Group’s Load Balancer to unused, follow these steps.

Caution
  • Please be careful as there may be service impact when separating or connecting servers from the Load Balancer.
  • If Draining Timeout is in use, setting the Load Balancer to unused or removing some of the attached Load Balancers with the X button will not detach immediately. After waiting for the Draining Timeout (seconds), the server is detached from the Load Balancer. At that time, the Auto-Scaling Group remains in the Detach from LB state.
  1. Click the All Services > Compute > Virtual Server menu. Go 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 change the Load Balancer to unused. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
  5. Click the Edit button of the Load Balancer. The Load Balancer Edit popup opens.
  6. Load Balancer edit Choose whether to use it in the popup window. If you deselect Use, Load Balancer will no longer be used.
  7. Use deselection, and click the Confirm button. Load Balancer Modification Notification popup opens. Verify the message in the notification popup and click the Confirm button.

Delete Auto-Scaling Group

Deleting an unused Auto-Scaling Group can reduce operational costs. However, terminating an Auto-Scaling Group may cause the running service to stop immediately, so you should thoroughly consider the impact of service interruption before proceeding with the termination.

Caution
Please note that data cannot be recovered after deleting the service.

To terminate 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 terminate. Navigate to the Auto-Scaling Group Details page.
  4. Click the Auto-Scaling Group Delete button.
  5. After the deletion is complete, verify that the resource has been removed on the Auto-Scaling Group List page.

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. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

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

  3. On the Launch Configuration list page, click the Create Launch Configuration button. You will be taken to the Create Launch Configuration page.

  4. On the Launch Configurationp Creation page, in the Image and Version Selection area, select the required information and click the Next button.

    Reference
    Please refer to the server type in Virtual Server OS Image Provisioning Versions for images selectable in Launch Configuration.

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

    Category
    Required status
    Detailed description
    Launch Configuration nameRequiredLaunch Configuration name
    • Name used to distinguish the Launch Configuration
    Service Type > Server TypeRequiredLaunch Configuration server type
    • Standard: Standard specifications commonly used
    • High Capacity: Large-scale server specifications beyond Standard
    Block StorageRequiredConfigure 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, and 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
        • Performance degradation occurs when using the SSD_KMS disk type
    • 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 GB to 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
        • Performance degradation occurs when using the SSD_KMS disk type
      • SSD_MultiAttach: Volume that can be attached to more than one server
    KeypairRequiredSelect 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 required
    • Default login account list by OS
      • Alma Linux: almalinux
      • RHEL: cloud-user
      • Rocky Linux: rocky
      • Ubuntu: ubuntu
      • Windows: sysadmin
    File Storage SettingsSelectionScale-out/Scale-in can be set to automatically connect File Storage
    • Volume: After clicking the Select button, choose the Volume to use in the Select File Storage popup
    • Up to 5 can be selected
    • The selected Volume can be deleted 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
    Detailed description
    Init ScriptSelectionScript that runs when the server of 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.
    tagSelectionAdd Tag
    • Up to 50 can be added per resource
    • After clicking the Add Tag button, enter or select Key, Value values
    Table. Launch Configuration additional information input fields

  7. Verify creation information Check the information you entered on the page and the estimated amount, and click the Create button.

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

View Launch Configuration Details

The Launch Configuration service allows you to view and edit the full list of resources and detailed information. Launch Configuration Details page consists of Details, Tags, Activity Log tabs.

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

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. Click the Launch Configuration menu. Navigate to the Launch Configuration List page.
  3. On the Launch Configuration List page, click the resource you want to view detailed information for. You will be taken to the Launch Configuration Details 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.
      CategoryDetailed description
      Launch Configuration statusUser-created Launch Configuration status
      • Active: Available
      Delete Launch ConfigurationDelete 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 edit the information if needed.

CategoryDetailed description
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Launch Configuration, it refers to the Launch Configuration SRN
Resource nameResource name
  • In a Launch Configuration, it refers to the Launch Configuration name
Resource IDUnique resource ID in the service
constructorUser who created the service
Creation date and timeService creation date and time
editorUser who edited the service information
Modification dateDate and time the service information was modified
Launch Configuration nameLaunch Configuration name
imageWhen creating a Launch Configuration, the selected image name
  • . This is the OS image used when launching servers in the Auto Scaling Group that uses this Launch Configuration.
Number of Auto-Scaling GroupsNumber of Auto Scaling Groups using a Launch Configuration
Server typeServer type set in Launch Configuration
Block StorageBlock Storage information per server configured in the Launch Configuration
  • type, capacity, kind
KeypairServer authentication information set in the Launch Configuration
  • Keypair information used to connect to the servers of the Auto Scaling Group that uses this Launch Configuration
Init ScriptThe Init Script set in the Launch Configuration
  • is the script that runs when a server in an Auto-Scaling Group using that Launch Configuration starts.
File Storage SettingsFile Storage Volume name set in the Launch Configuration
  • Click the Volume name to view detailed File Storage information
Table. Launch Configuration Details Tab Items

tag

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

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Launch Configuration Tag Tab Items

Work History

You can view the operation history of the selected resource on the Launch Configuration List page.

CategoryDetailed description
Task History ListResource Change History
  • Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Check Operator Information
Table. Launch Configuration Job History Tab Detailed Information Items

Delete Launch Configuration

Deleting unused Launch Configurations can reduce operational costs. However, terminating a Launch Configuration may cause running services to stop immediately, so you should carefully consider the impact of service interruption before proceeding with the termination.

Caution
Please be careful, as data cannot be recovered after deletion.

To delete a Launch Configuration, follow these steps.

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. Click the Launch Configuration menu. Go to the Launch Configuration List page.
  3. On the Launch Configuration List page, click the resource to be terminated. Navigate to the Launch Configuration Details page.
  4. Launch Configuration Delete Click the button.
  5. After deletion is complete, verify on the Launch Configuration List page that the resource has been removed.
Caution
A Launch Configuration attached to an Auto-Scaling Group cannot be deleted. Please delete the Launch Configuration after first deleting the Auto-Scaling Group.

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
    CategoryRequiredPolicy Category
    • Scale In: return server count
    • Scale Out: increase server count
    Policy NameRequiredName for policy-specific categorization
    Execution conditionsRequiredConditions 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 unitRequiredPolicy 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
    cooldownRequiredThe 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.

Policy example description 1
CategoryExecution Conditionsexecution unitcooldown
Scale OutAverage CPU Usage >= 60% occurs for 1 minuteIncrease the server count by the specified number, incrementing by one unit.300 seconds
Table. Auto-Scaling Group policy example 1
  • If the average CPU usage of the servers in the Auto-Scaling Group exceeds 60% for one minute, a server is added one at a time.
  • When a server is added, the cooldown period is 300 seconds, and during this time, no server addition or removal due to policy occurs.
  • After the cooldown period ends, the policy execution conditions are checked again.
Policy example description 2
CategoryExecution Conditionsexecution unitcooldown
Scale InMin CPU Usage <= 5% occurs for 1 minuteScale the number of servers up or down by the specified ratio, returning 50%.300 seconds
Table. Auto-Scaling Group policy example 2
  • If the minimum CPU usage of servers in the Auto-Scaling Group remains below 5% for 1 minute, 50% of the current servers will be terminated.
  • When a server is terminated, the cooldown period is 300 seconds, and during this time, no server additions or removals occur due to policy.
  • After the cooldown period ends, the policy execution conditions are checked again.
Policy example description 3
CategoryExecution ConditionsExecution Unitcooldown
Scale OutMax CPU Usage >= 90% occurs for 1 minuteFix the number of servers to 5 based on the entered value300 seconds
Table. Auto-Scaling Group policy example 3
  • If the maximum CPU usage among the servers in the Auto-Scaling Group exceeds 90% for 1 minute and the current number of servers is less than 5, servers will be created up to a total of 5.
  • During server creation, the cooldown period is 300 seconds, and no server additions or removals due to policy occur during the cooldown period.
  • After the cooldown period ends, the policy execution conditions are checked again.

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
    CategoryRequiredPolicy Classification
    • Scale In: Return server count
    • Scale Out: Increase server count
    Policy NameRequiredName for policy-specific categorization
    Execution conditionsRequiredConditions 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 unitRequiredPolicy 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 downRequiredThe 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.

Policy classificationPolicy NameExecution Condition(Statistic)Execution condition(Metric type)Execution condition range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy Constraint Example 1 - Pre-registration Policy

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).

Policy classificationPolicy NameExecution condition(Statistic)Execution condition(Metric type)Execution condition range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy Constraint Example 2 - Pre-registration Policy

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.

Policy ClassificationPolicy NameExecution Condition(Statistic)Execution condition(Metric type)Execution condition range
Scale InAddUpdatePolicyAverageCPU Usage<= 60%
Table. Policy Constraint Example 2 - Non-Addable Policy

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).

Policy classificationPolicy NameExecution condition(Statistic)Execution condition (Metric type)Execution condition range
Scale InScaleInPolicyAverageCPU Usage<= 10%
Table. Policy Constraint Example 3 - Pre-registration Policy

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.

Policy classificationPolicy NameExecution Condition(Statistic)Execution condition(Metric type)Execution condition range
Scale OutAddUpdatePolicy1AverageCPU Usage< 60%
Scale OutAddUpdatePolicy2AverageCPU Usage<= 60%
Scale OutAddUpdatePolicy3AverageCPU Usage>= 10%
Scale OutAddUpdatePolicy4AverageCPU Usage> 9%
Table. Policy constraint example 3 – non‑addable policy

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.

Policy classificationPolicy NameExecution Condition(Statistic)Execution condition (Metric type)Execution Condition Range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy Constraint Example 4 - Pre-registration Policy

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.

Policy classificationPolicy NameExecution Condition(Statistic)Execution condition (Metric type)Execution condition range
Scale InAddUpdatePolicy1AverageCPU Usage<= 10%
Scale InAddUpdatePolicy2MinCPU Usage<= 60%
Table. Policy constraint example 4 – Addable policy

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 nameRequiredName to distinguish by schedule
    Select server countRequiredSelect 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 serversRequiredEnter 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)
    PeriodRequiredSchedule 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 dateSelectionSet schedule start date
    • Cannot set a date earlier than the current date. The default is the current date.
    End dateSelectionSet schedule end date
    • Cannot set a date earlier than the current date. The default is the current date plus 7 days.
    permanentSelectionWhen configuring permanently, set the schedule end date to 9999-12-31
    timeRequiredSchedule execution time setting
    • Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
    time zoneRequiredSchedule execution time zone (example: Asia/Seoul (GMT +09:00))
    day of the weekRequiredWhen Period is set to Weekly, select the Day of the week to execute the schedule
    DateRequired
    • 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.
Reference

If you select the schedule frequency as monthly, you must enter the schedule execution date, Date. Refer to the information below to register the schedule.

  • If you input a number greater than 0, it represents the day of the month.
    • Example: If you enter 1, you get August 1, September 1, …, December 1
  • If you enter a number less than 0, the calculation starts from the end of each month.
    • Entering -1 means the last day of each month.
      • Example: August 31, September 30, …, December 31
    • If you enter -2, it means the day before the last day of each month.
      • Example: August 30, September 29, …, December 30
    • Since the last day of each month varies—31, 30, 29, or 28 days—we allow calculation from the end of the month using negative numbers, as shown above, to handle schedules that need to run on the month’s final day.
Information
  • When the schedule runs, if the Min server count set in the schedule is greater than the Desired server count, or if the Max server count is less than the Desired server count, the Desired server count is also adjusted.
  • If there are schedules with overlapping execution times, they may not run correctly. Please try to avoid overlapping execution times as much as possible.

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 nameRequiredName to distinguish by schedule
    Select number of serversRequiredSelect 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 serversRequiredEnter 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)
    periodRequiredSchedule 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 dateSelectionSet schedule start date
    • Cannot set a date earlier than the current date. The default is the current date.
    End dateSelectionSet schedule end date
    • Cannot set a date earlier than the current date. The default is the current date plus 7 days.
    PermanentSelectionWhen configuring permanently, set the schedule end date to 9999-12-31.
    timeRequiredSchedule execution time setting
    • Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
    time zoneRequiredSchedule execution time zone (example: Asia/Seoul (GMT +09:00))
    day of the weekRequiredWhen Period is weekly, select the day of the week to run the schedule.
    DateRequired
    • 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.

Reference
  • The notification method (E-mail or SMS) can be set on the Notification Settings page by selecting Notification Target as Service > Virtual Server Auto-Scaling.
  • For details on editing notification settings, refer to Edit Notification Settings.

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.
    CategoryDetailed description
    Notification timingNotification 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 recipientUser 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
Caution
When adding a notification recipient, verify that an email address exists and add it. Only users with login history (users who have registered an email or mobile phone number) can receive notifications.
  1. 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.
    CategoryDetailed description
    Notification timingNotification 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.