The page has been translated by Gen AI.

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.
ServiceWatch Metrics
Launch Configuration