The page has been translated by Gen AI.

How-to guides

Users can create the service by entering the required information for the 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. Refer to Launch Configuration 생성하기.

To create an Auto-Scaling Group, 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. Click the Auto-Scaling Group menu. 2. Auto-Scaling Group List Navigate to the page.

  3. On the Auto-Scaling Group List page, click the Create Auto-Scaling Group button. 3. Auto-Scaling Group Creation Navigate to the 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.
      • Click the Launch Configuration creation button to create a new Launch Configuration.
    • Enter or select the required information in the Service Information Input area.
      Category
      required status
      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
      • Automatically assign a server name by combining the entered server name, which serves as an identifier to distinguish servers created within the Auto-Scaling Group, with a sequence
      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-Scailg Group should maintain
      • Desired: Set the target number of servers within the Auto-Scailg Group; also indicates the number of servers initially created when the Auto-Scailg Group is created
      • Max: Set the maximum number of servers the Auto-Scailg Group can maintain
      • After creating the Auto-Scaling Group, you can adjust the settings using the Edit button. For details, see 서버 수 수정하기
      Desired server count manual settingSelectionSelect whether to manually change the Desired server count
      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
      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 the 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 cleanup
        • If the Load Balancer is unused, Draining Timeout cannot be configured
        • The default is 300 seconds; you can enter values from a minimum of 1 second up to a maximum of 3,600 seconds.
      Table. Auto-Scaling Group service information entry items
    • In the Scaling policy configuration area, set the Scaling policy.
      • For detailed information on policy settings, see 정책 추가하기.
        Category
        required status
        Detailed description
        Current settingSelectionSet the Scaling policy now
        • Add Policy button click displays policy information input fields
        Set laterSelectionAfter creating an Auto-Scaling Group, set the policy on the details page
        Table. Auto-Scaling Group Scaling policy configuration items
    • In the Notification Settings area, configure the notification recipients and notification method.
      • For detailed information about notification settings, refer to 알림 추가하기.
        Category
        required status
        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 on notification settings, refer to the details
        • You can modify notification information by clicking the Edit button in the notification recipients list
        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 in an Unhealthy state
      • 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
      • Add Tag button after clicking, 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, verify the created Auto-Scaling Group on the Auto-Scaling Group list page.

Auto-Scaling Group Check detailed information

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

To view detailed information about the Auto-Scaling Group, follow these steps.

  1. All Services > Compute > Virtual Server menu, click. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Navigate to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to view detailed information. 3. Go to the Auto-Scaling Group Details page.
    • Auto-Scaling Group Details The page displays status information and additional feature information, and Details, Policies, Schedule, Virtual Server, Load Balancer, Tags, Operation History are organized as tabs.
      CategoryDetailed description
      Auto-Scaling Group statusStatus of the Auto-Scaling Group created by the user
      • Creating: Creating Auto-Scaling Group
      • In Service: In Service
      • 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 allows you to view detailed information of the selected resource and, if needed, modify the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Auto-Scaling Group, it means the Auto-Scaling Group SRN
Resource nameResource name
  • In an 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
ModifierUser who edited the service information
Modification date and timeDate 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 creating the Virtual Server of the Auto-Scaling Group
Number of serversCurrent number of servers created in the Auto-Scaling Group and the configured Min, Desired, Max server counts
Desired server count manual settingDesired server count manual setting enable/disable
VPCAuto-Scaling Group VPC information
Standard SubnetGeneral Subnet and NAT IP usage information for 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 an Unhealthy state
  • Virtual Server: Use is the default and cannot be changed
  • Load Balancer: Indicates usage when a Load Balancer is attached
    • Use*: When a Load Balancer is connected and health check is used
    • Not used: When a Load Balancer is connected and health check is not used
    • Use (does not operate because no LB is currently connected): When a Load Balancer is connected and health check is in use, but the Load Balancer has been detached
    • -: When no Load Balancer is connected
  • Grace period: Time to defer health checks
    • If 0, the health check grace period is not used
  • Click the Edit button to configure whether Load Balancer health check is used and set the Grace period. For details, see Change health check
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 list of policies for the selected resource and, if needed, add or manage policies.

CategoryDetailed description
CategoryPolicy Type
  • Scale In: Return server count
  • Scale Out: Increase server count
Policy NameName for policy classification
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, 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 met for N minutes for the policy to execute)
execution unitPolicy 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
CooldownThe waiting time (seconds) when a server is started or terminated due to a policy
  • The default is 300 seconds, configurable from a minimum of 1 second up to a maximum of 3,600 seconds
More > EditModify the policy information
More > ActivateEnable this policy
  • Can be selected only when the policy is disabled
More > DisableDisable this 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 정책 관리하기.

Schedule

Auto-Scaling Group List page allows you to view the schedule list of the selected resources 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/DaySchedule execution date or day of week
  • Date/Day selected according to the schedule cycle
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 > DisableDisable 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 on schedule management, refer to 스케줄 관리하기.

Virtual Server

On the Auto-Scaling Group List page, you can view the Virtual Server list of the selected resource.

CategoryDetailed description
Server nameServer name created in the Auto-Scaling Group
  • Server name when clicked, navigate 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 found in the Operation History tab
Table. Auto-Scaling Group Details - Virtual Server Tab Items

Load Balancer

Auto-Scaling Group List page allows you to view the Load Balancer list of the selected resources, and, if necessary, you can add or manage Load Balancers.

CategoryDetailed description
Draining TimeoutWhether to use Draining Timeout
  • 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
  • When you click the Edit button, set the Load Balancer usage
  • If it is already in use, add or modify 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 groupLoad Balancer’s LB server group
  • 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

On the Auto-Scaling Group List page, you can 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 a notification 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
  • On success: Whether to send when termination succeeds
  • On failure: Send when termination fails
When the policy execution condition is metWhether a notification is triggered when the policy execution conditions are met
statusNotification activation status
  • Active: enabled
More > EditEdit the notification information
More > ActivateEnable this notification information
  • Can be selected only when the notification is disabled
More > DisableDisable the notification information
  • Can be selected only when the notification is enabled
Add notificationAdd a new notification
DeleteDelete the selected notification from the list
Table. Auto-Scaling Group Details - Notification Tab Items
Reference
For detailed information about notification settings, refer to 알림 관리하기.

Tag

On the Auto-Scaling Group List page, you can 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. Auto-Scaling Group Details - Tag Tab Items

Operation History

Auto-Scaling Group List page allows you to view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation Timestamp, 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 management functions for the created Auto-Scaling Group, you can perform tasks on the Auto-Scaling Group Details page.

Edit Launch Configuration

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

참고
Even if you modify the Launch Configuration, it does not apply to servers already created in the Auto-Scaling Group; it only takes effect for servers created thereafter. If you want to apply the updated Launch Configuation to all servers in the Auto-Scaling Group, set the server count (Desired) to 0 to delete all existing servers, then change the server count (Desired) to the desired amount.

To modify the Launch Configuration of an Auto-Scaling Group, 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 Auto-Scaling Group menu. 2. Go to the Auto-Scaling Group List page.

  3. On the Auto-Scaling Group List page, click the resource to edit the Launch Configuration. 3. Auto-Scaling Group Details Navigate to the page.

  4. Click the Edit button for the Launch Configuration name. 4. Launch Configuration Edit The popup window opens. 4. 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
    Auto-Scaling Group countNumber of Auto-Scaling Groups with a Launch Configuration applied
    View DetailsButton to view Launch Configuration details
    Table. Launch Configuration list items

  5. Launch Configuration Edit In the popup window, select the Launch Configuration to change, then click the Confirm button. 5. Launch Configuration Modification Notification A popup window opens. 5. Launch Configuration Modification Notification Check the message in the popup window and click the Confirm button.

Modify server count

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

Reference
The maximum number of servers that can be configured is 20. However, when a Load Balancer is present, exclude servers that are not connected to the Load Balancer.

To modify the number of servers in an Auto-Scaling Group, 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 Auto-Scaling Group menu. 2. Navigate to the Auto-Scaling Group List page.
  3. On the Auto-Scaling Group List page, click the resource to modify the server count. 3. Go to the Auto-Scaling Group Details page.
  4. Click the Edit server count button. 4. Edit Server Count popup window opens.
  5. Edit Server Count After entering the required fields in the popup window, click the Confirm button.
    Category
    required status
    Detailed description
    Number of servers > MinRequiredMinimum number of servers to modify
    • Set the number of servers that the Auto-Scaling Group maintains at a minimum
    Number of servers > DesiredRequiredNumber of target servers to modify
    • Set the number of target servers within the Auto-Scaling Group
    Number of servers > MaxRequiredTarget number of servers to modify
    • Set the number of servers that the Auto-Scailg Group can maintain at maximum
    Table. Auto-Scailg Group server count modification items

Terminate Virtual Server Created by Auto-Scaling Group

Virtual Server created in the Auto-Scaling Group can be terminated by clicking the Terminate button on its detail page or by modifying the server count.

Caution
  • Please note that 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, the Virtual Server cannot be terminated.
Reference
  • If you terminate a Virtual Server created in the 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: If you terminate the Virtual Server, the volume will be deleted. * However, if a Snapshot exists, it will not be deleted even if Delete on termination is set.
    • Multi-attach volume: It can only be deleted when the server you are trying to delete 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. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
  3. On the Virtual Server List page, select the Virtual Server created by the Auto-Scaling Group. 3. Navigate to the Virtual Server Details page.
  4. On the Virtual Server Details page, click the Service Cancellation button. 4. A popup window announcing the server termination opens.
  5. Confirm Click the button. 5. Server termination is complete.

Terminate by adjusting the server count

To terminate a Virtual Server by adjusting the server count, follow the steps below.

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Go to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to terminate the Virtual Server. 3. Auto-Scaling Group Details page.
  4. Click the Edit button for the Server Count item. 4. Edit Server Count popup window opens.
  5. Server Count Modification In the popup window, after reducing the Desired count, click the Confirm button. 5. When the desired number of servers is adjusted, the Virtual Server is terminated.
Notice
  • Desired server count manual setting is unused, you cannot modify the Desired server count. * To modify the Desired server count, refer to Desired 서버 수 수동 설정 수정하기.
  • When a Virtual Server is terminated, the Desired server count remains unchanged, and scale-out proceeds according to the Desired check batch.

Manually modify the desired number of servers

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

Reference
If you do not select Use for manual Desired server count setting, you cannot modify the Desired server count in the details’ server count edit. The desired number of servers 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. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Navigate to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to manually change the Desired server count. 3. Auto-Scaling Group Details Navigate to the page.
  4. Click the Edit server count button. 4. Desired server count manual setting The popup window opens.
  5. Desired server count manual setting After selecting whether to use it in the popup window, click the Confirm button.

Setting up Security Group

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

Reference
Even if you modify the Security Group, it does not apply to servers already created in the Auto-Scaling Group; it only applies to servers created thereafter. If you want 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 again.

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

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

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

  3. Auto-Scaling Group List page, click the resource to configure the Security Group. 3. Go to the Auto-Scaling Group Details page.

  4. Click the Edit button for Security Group. 4. Security Group Edit The popup window opens. 4. 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. 5. Security Group Modification Notification A popup window opens. 5. Security Group Modification Alert Check the message in the popup window and click the Confirm button.

Change status check

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

Caution
  • The Load Balancer status check feature can be used only when a Load Balancer is in use.
  • 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.
To change whether the Load Balancer health check feature of an Auto-Scaling Group is enabled, 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 Auto-Scaling Group menu. 2. Go to the Auto-Scaling Group List page.
  3. On the Auto-Scaling Group List page, click the resource to modify the Load Balancer health check feature. 3. Navigate to the Auto-Scaling Group Details page.
  4. Click the Edit button of Status Check. 4. Edit Status Check The 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.

Auto-Scaling Group Manage Additional Information

You can set the Auto-Scaling Group’s Load Balancer to enabled and select the LB server group. For an Auto-Scaling Group that uses a Load Balancer, you can set it to unused.

Load Balancer Draining Timeout Edit

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

Reference

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

  • Because sessions may remain connected to the server, setting a Draining Timeout and waiting can clean up sessions more safely.
  • If the Load Balancer is unused, the 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 for an Auto-Scaling Group, follow these steps.

  1. All Services > Compute > Virtual Server menu, click it. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Go to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to configure the Load Balancer Draining Timeout. 3. Auto-Scaling Group Details Navigate to the page.
  4. Load Balancer Click the tab. 4. Load Balancer Navigate to the list page.
  5. Click the Edit button of Draining Timeout. 5. Draining Timeout Edit A popup window opens.
  6. Edit Draining Timeout In the popup window, select whether to use Draining Timeout, and enter the Draining Timeout duration (seconds).
  7. Draining Timeout Edit After checking the input value in the popup window, click the Confirm button. 7. Draining Timeout Modification Notification A popup window opens. 7. 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 in use, after waiting for the Draining Timeout (seconds), the server is removed from the LB server group’s members.
  • In the case of Member separation due to Load Balancer modification, it waits in Detach from LB state, and in the case of Member separation due to Scale In, it waits in Scale In state.
  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Navigate to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to use with Load Balancer. 3. Go to the Auto-Scaling Group Details page.
  4. Load Balancer Click the tab. 3. Load Balancer Navigate to the list page.
  5. Click the Edit button of the Load Balancer. 4. Load Balancer Edit The popup window opens.
  6. Edit Load Balancer Please select whether to use it in the popup window. 5. If you select Use, you can select 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. * A maximum of three is allowed. * You can remove the Load Balancer you added by clicking the X button.
  7. Check the Load Balancer list and click the Confirm button. 6. Load Balancer Modification Notification A popup window opens. 6. Check the message in the notification popup and click the Confirm button.
Caution
  • Please be aware that separating or connecting servers from the Load Balancer may impact the service.
  • If the Draining Timeout is in use, setting the Load Balancer to unused or removing some of the connected Load Balancers with the X button will not disconnect them immediately. * After waiting for the Draining Timeout (seconds), the server is detached from the Load Balancer. * At this point, the Auto-Scaling Group waits in the Detach from LB state.
Reference

Load Balancer Not Used

You can modify the Auto-Scaling Group’s Load Balancer to be disabled. To configure an Auto-Scaling Group without using a Load Balancer, follow these steps.

Caution
  • Please be aware that separating or connecting servers from the Load Balancer may impact the service.
  • If the Draining Timeout is in use, setting the Load Balancer to not used or removing some of the connected Load Balancers with the X button will not detach them immediately. * After waiting for Draining Timeout(seconds), the server is detached from the Load Balancer. * At this point, the Auto-Scaling Group waits in the Detach from LB state.
  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Auto-Scaling Group List Navigate to the page.
  3. On the Auto-Scaling Group List page, click the resource to set the Load Balancer to unused. 3. Auto-Scaling Group Details page.
  4. Load Balancer Click the tab. 4. Load Balancer Navigate to the list page.
  5. Click the Edit button of Load Balancer. 5. Load Balancer Edit The popup window opens.
  6. Edit Load Balancer Select whether to use it in the popup window. 6. If you deselect 사용, you will no longer use the Load Balancer.
  7. Uncheck the Use option and click the Confirm button. 7. Load Balancer Modification Notification A popup window opens. 7. Check the notification popup message and click the Confirm button.

Delete Auto-Scaling Group

Deleting unused Auto-Scaling Groups can reduce operating costs. However, if you terminate the Auto-Scaling Group, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact of service interruption.

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

To terminate the Auto-Scaling Group, follow these steps.

  1. All Services > Compute > Virtual Server menu, click it. 1. Navigate to the Service Home page of the Virtual Server.
  2. Click the Auto-Scaling Group menu. 2. Go to the Auto-Scaling Group List page.
  3. Auto-Scaling Group List page, click the resource to terminate. 3. Go to the Auto-Scaling Group Details page.
  4. Click the Auto-Scaling Group Delete button.
  5. After the deletion is complete, verify on the Auto-Scaling Group List page that the resource has been deleted.
ServiceWatch Metrics
Launch Configuration