A scaling group is a collection of Elastic Compute Service (ECS) instances or elastic container instances that can be used for similar business scenarios. When you create a scaling group, you can specify the minimum and maximum numbers of instances, templates that are used for scale-out, and policies that are used for scale-in. You can use a scaling group to manage a group of instances based on your business requirements. This topic describes how to create, view, modify, delete, disable, and enable scaling groups.

Prerequisites

The following table describes the items that you need to take note of when you create a scaling group.

Scenario Usage notes
You want to use Auto Scaling. Auto Scaling is activated. You must follow the on-screen instructions to activate Auto Scaling. For more information, see Manage the service-linked role for Auto Scaling.
You want Auto Scaling to create ECS instances based on a launch template. A launch template is created. For more information, see Create a launch template.
You want to associate a Classic Load Balancer (CLB) instance with a scaling group.
  • One or more CLB instances are created and in the Active state. For more information, see Create and manage a CLB instance.
  • The CLB instance and the scaling group must reside in the same region.
  • If the network type of the CLB instance and the scaling group is virtual private cloud (VPC), the CLB instance and the scaling group must reside in the same VPC.
  • If the network type of the CLB instance is classic network, the network type of the scaling group is VPC, and the backend server group of the CLB instance contains ECS instances that reside in a VPC, the ECS instances and the scaling group must reside in the same VPC.
  • The CLB instance is associated with at least one listener. For more information, see Listener overview.
  • The health check feature is enabled for the CLB instance. For more information, see Configure and manage health checks.
You want to associate an Application Load Balancer (ALB) instance with a scaling group.
  • The network type of the scaling group must be VPC. The scaling group and the ALB server group must reside in the same VPC.
  • The ALB server group is in the Available state.
You want to associate an ApsaraDB RDS instance with a scaling group.
  • One or more ApsaraDB RDS instances are created and in the Running state. For more information, see What is ApsaraDB RDS?.
  • The scaling group and the ApsaraDB RDS instance must reside in the same region.

Create scaling groups

  • You can create only a limited number of scaling groups in a region. To view the quota or request a quota increase, go to Quota Center.
  • When you create a scaling group, you must configure the Minimum Number of Instances and Maximum Number of Instances parameters. You can configure the Expected Number of Instances parameter based on your business requirements.
    • If you do not configure the Expected Number of Instances parameter and set the Minimum Number of Instances parameter to a value greater than 0 when you create a scaling group, Auto Scaling triggers a scale-out activity to add the required number of instances to reach the minimum number in the case that the number of existing instances in the scaling group is less than the value of the Minimum Number of Instances parameter.
    • If you set the Expected Number of Instances parameter to a value greater than 0 and the number of existing instances in the scaling group is less than the value of the Expected Number of Instances parameter, Auto Scaling triggers a scale-out activity to reach the expected number of instances.
    • If the number of existing instances in the scaling group is greater than the value of the Maximum Number of Instances parameter, Auto Scaling triggers a scale-in activity to remove excess instances from the scaling group until the number of instances is equal to the maximum number of instances.
    Note Auto Scaling triggers the preceding scaling activities without the need to execute scaling rules.
  1. Log on to the Auto Scaling console.
  2. In the top navigation bar, select a region.
  3. In the left-side navigation pane, click Scaling Groups.
  4. In the upper-left corner of the Scaling Groups page, click Create.
  5. Configure the following parameters for the scaling group and click OK.
    The following table describes the parameters.
    Parameter Description
    Scaling Group Name The name of a scaling group must be 2 to 64 characters in length, and can contain letters, digits, periods (.), underscores (_), and hyphens (-). The name must start with a letter or a digit.
    Type The type of the instances that provide computing resources in the scaling group. Auto Scaling scales instances based on the Type parameter. Valid values:
    • ECS: ECS instances
    • ECI: elastic container instances
    Instance Configuration Source Auto Scaling creates instances based on the Instance Configuration Source parameter. Valid values:
    • Launch Templates: A launch template contains information such as the key pair, RAM role, instance type, and network settings. A launch template does not contain passwords. The Launch Templates setting is available only if you set the Type parameter to ECS.

      After you set the Instance Configuration Source parameter to Launch Templates, you must also configure the Select Launch Template parameter and the Select Template Version parameter. To meet diverse business requirements, you can specify multiple instance types in the Extend Configurations of Launch Template section. For more information about how to configure weights for instance types, see Use performance metrics to measure Auto Scaling.

    • Select Existing Instance: You must select an existing instance before Auto Scaling extracts the basic configurations of the instance to create a default scaling configuration.

      If you set the Type parameter to ECS, the basic configurations that are extracted from the selected ECS instance include the instance type, network type, security group, and base image. The instance logon password and tags are not included. The base image is the image used by the existing instance. The base image does not include instance data such as application data. If you want to include all system configurations of the instance and instance data in the scaling configuration, create a custom image for the instance and use the custom image to update the image of the scaling configuration. For more information, see Image update in scaling configurations.

    • Create from Scratch: You do not need to specify a template that is used to automatically create instances. Specify a scaling configuration or launch template only after you create the scaling group. The steps that you must perform to create a scaling configuration vary based on the value of the Type parameter. For more information, see Create a scaling configuration (ECS) and Create a scaling configuration (Elastic Container Instance).
    Note When you create a scaling group that contains ECS instances created in the ECS console, the instance configurations and network type of the instances are automatically populated. We recommend that you use the default settings of these instances.
    Tag You can add tags to help you find and manage scaling groups. For more information, see Overview.
    Note The tags that you add apply only to the scaling group. If you want to add tags to an instance in the scaling group, specify the tags in the scaling configuration or in the launch template.
    Tags Propagated to Instances During Scale-out After you configure the Tag parameter, you can configure this parameter to specify one or more tags that you want to propagate to instances in the scaling group.
    Scale-In Policy If you want to remove instances from the scaling group, Auto Scaling removes instances based on the Scale-In Policy parameter. If multiple instances meet the removal conditions after the scale-in policy is applied, a random instance is removed. The Scale-In Policy parameter is available only if you set the Type parameter to ECS.
    The Scale-In Policy parameter contains the First Remove and Then Remove fields. Specify different values for the two fields. The following part describes the values.
    Note If you set the Type parameter to ECI, Auto Scaling removes the instances that are created based on the earliest scaling configuration. Then, Auto Scaling removes the instances that are created at the earliest point in time from the results obtained based on the First Remove field.
    • Earliest Instance Created Using Scaling Configuration: Auto Scaling removes instances that are created based on the earliest scaling configuration or launch template. No scaling configuration or launch template is associated with manually added instances. Therefore, manually added instances are not removed first. If more instances need to be removed from a scaling group after Auto Scaling removes all instances with which the earliest scaling configuration or launch template is associated, Auto Scaling removes manually added instances at random.
      Note Scaling Configuration Source in the Earliest Instance Created Using Scaling Configuration setting can be a scaling configuration or a launch template.

      The version of a launch template does not indicate the order in which the template is added. For example, if you use the lt-foress V2 template to create a scaling group, and then replace the template with the lt-foress V1 template when you modify the scaling group, Auto Scaling considers the lt-foress V2 launch template as the earliest template.

    • Earliest Created Instance: Auto Scaling removes the instances that are created at the earliest point in time.
    • Most Recent Created Instance: Auto Scaling removes the instances that are created at the latest point in time.
    • No Policy: This setting is available only for the Then Remove field. If you select No Policy, Auto Scaling does not remove instances from the results obtained based on the First Remove field.
    If Auto Scaling removes instances based on the Earliest Instance Created Using Scaling Configuration setting, you can select one of the following values for the Then Remove field:
    • No Policy: Auto Scaling does not remove instances from the results obtained based on the First Remove field.
    • Earliest Created Instance: Auto Scaling removes the instances that are created at the earliest point in time from the results obtained based on the First Remove field.
    • Most Recent Created Instance: Auto Scaling removes the instances that are created at the latest point in time from the results obtained based on the First Remove field.
    Note The value of the Scaling Policy parameter also affects how instances are removed from scaling groups. For more information about how to remove ECS instances from scaling groups, see Configure a combination policy for removing instances.
    Suspend Process You can suspend processes before you perform specific operations. For example, you can suspend the health check process before you stop an instance. This way, the instance is not removed from the scaling group if the health check fails. You can suspend the following processes for a scaling group:
    • Scale-out: If you suspend this process, Auto Scaling rejects all scale-out requests.
    • Scale-in: If you suspend this process, Auto Scaling rejects all scale-in requests.
    • Health Check: If you suspend this process, Auto Scaling suspends the health check process and does not remove unhealthy instances.
    • Scheduled Task: If you suspend this process, the scaling rules that are associated with a scheduled task are not executed when the execution time of the scheduled task arrives.
    • Event-triggered Task: If you suspend this process, the scaling rules that are associated with an event-triggered task are not executed when the event-triggered task enters the alert state.

    For more information, see Suspend and resume scaling processes.

    Deletion Protection After you enable this feature, you cannot delete the scaling group by using the Auto Scaling console or by calling API operations. This helps prevent misdeletion of scaling groups.
    Instance Health Check After you enable this feature, Auto Scaling checks the status of instances on a regular basis. If an instance does not run as expected, the instance is considered unhealthy and is removed from the scaling group. For more information, see Instance lifecycles.
    Minimum Number of Instances If the number of instances in the scaling group is less than the value of this parameter, Auto Scaling adds instances until the number of instances in the scaling group reaches the minimum number.
    Maximum Number of Instances If the number of instances in the scaling group is greater than the value of this parameter, Auto Scaling removes instances until the number of instances in the scaling group does not exceed the maximum number.
    Expected Number of Instances If you specify an expected number of instances for the scaling group, Auto Scaling maintains the number of instances based on the value of the Expected Number of Instances parameter. For more information, see Expected number of instances.
    Note You can enable the Expected Number of Instances feature only when you create a scaling group. You cannot enable the Expected Number of Instances feature for a scaling group after you create it.
    Maximum Life Span of Instance (Seconds) This parameter specifies the maximum life span of instances in the scaling group. After the specified life span of instances expires, Auto Scaling creates new instances to replace the instances.

    This parameter is available only if you set the Type parameter to ECS.

    Default Cooldown Time (Seconds) This parameter specifies the default cooldown time for the scaling group after a scaling activity is triggered. During the cooldown time, Auto Scaling rejects all requests for scaling activities triggered by event-triggered tasks. Scaling activities that are triggered by other types of tasks such as scheduled tasks and manually executed tasks are not subject to the cooldown time and can be immediately executed.
    Network Type The Scaling Policy, Instance Reclaim Mode, and Associate ALB Server Group parameters are available only if you set Network Type to VPC.
    Note When you create a scaling group that contains ECS instances created in the ECS console, the instance configurations and network type of the instances are automatically populated. We recommend that you use the default settings of these instances.

    A scaling group and instances in the scaling group must belong to the same network type. For example, if a scaling group resides in a VPC, the instances in the scaling group must also reside in the VPC. If a scaling group resides in the classic network, the instances in the scaling group must also reside in the classic network.

    Note After you create a scaling group, you cannot change the network type of the scaling group.
    Scaling Policy The Scaling Policy parameter is available only if you set Type to ECS and Network Type to VPC. Valid values:
    • Priority Policy: Auto Scaling preferentially creates instances in the zone where the vSwitch that has the highest priority resides. If the scaling fails, Auto Scaling creates instances in the zone where the vSwitch that has the next highest priority resides.
      Note If you set the Type parameter to ECI, Priority Policy is used by default.
    • Balanced Distribution Policy: This policy is valid only if the scaling group is associated with multiple vSwitches that are distributed across more than two zones. Auto Scaling evenly distributes instances across the zones where the vSwitches reside based on this policy. If instances are not evenly distributed across multiple zones due to insufficient resources, you can use Balanced Distribution Policy to re-distribute instances across zones. For more information, see Rebalance the distribution of ECS instances.
    • Cost Optimization Policy: This policy is valid only if you specify multiple instance types in the scaling configuration. When a scale-out activity is triggered, Auto Scaling preferentially creates ECS instances that have the lowest vCPU price. When a scale-in activity is triggered, Auto Scaling preferentially removes ECS instances that have the highest vCPU price. If you specify Preemptible Instance as the billing method in the scaling configuration, Auto Scaling preferentially creates preemptible instances. If preemptible instances cannot be created due to insufficient resources, Auto Scaling creates pay-as-you-go instances.
      If you select Cost Optimization Policy, configure the following parameters based on your business requirements:
      • Minimum Pay-as-you-go Instances: the minimum number of pay-as-you-go ECS instances in the scaling group. Default value: 0. If the number of pay-as-you-go ECS instances in the scaling group is less than the value of Minimum Pay-as-you-go Instances, Auto Scaling preferentially creates pay-as-you-go instances.
      • Percentage of Pay-as-you-go Instances: the percentage of pay-as-you-go ECS instances among all automatically created instances. Default value: 70%. When you calculate this percentage, the pay-as-you-go ECS instances do not include the minimum number of pay-as-you-go ECS instances that you specify by using the Minimum Pay-as-you-go Instances parameter.
      • Lowest Cost Instance Types: the number of the instance types that have the lowest price. Default value: 1. This parameter is valid only if multiple instance types are specified in the scaling configuration. Auto Scaling evenly creates preemptible ECS instances of the instance types that are provided at the lowest price.
      • Enable Supplemental Preemptible Instances: After you enable the Supplemental Preemptible Instances feature, Auto Scaling automatically creates preemptible instances five minutes before the existing instances are reclaimed.
      • Use Pay-as-you-go Instances to Supplement Preemptible Capacity: By default, this feature is enabled. After you enable this feature, Auto Scaling creates pay-as-you-go instances to meet the required number of preemptible instances if preemptible instances cannot be created due to factors such as costs and insufficient resources.
    • Custom Combination Policy: You can combine the preceding policies to create a custom scaling policy. After you select the Custom Combination Policy setting, you must also configure the Percentage of Pay-as-you-go Instances parameter. You can configure the Multi-zone Balanced Distribution parameter and the Preemptible Capacity Planning Policy parameter based on your business requirements.
    Instance Reclaim Mode The Instance Reclaim Mode parameter is available only if you set the Type parameter to ECS and Network Type to VPC. Valid values:
    • Release: Instances that are removed from the scaling group are released. Resources of these instances are not retained. During a scale-out activity, Auto Scaling creates new instances and adds the instances to the scaling group.
      Note If you set the Type parameter to ECI, instances that are removed from the scaling group are released by default.
    • Economical Mode: ECS instances that are removed from the scaling group are stopped and enter Economical Mode. Some resources of the ECS instances are retained, and you are charged for these resources. During a scale-out activity, Auto Scaling preferentially adds the stopped ECS instances to the scaling group. After all stopped ECS instances are added, Auto Scaling determines whether to create ECS instances and add them to the scaling group based on your scale-out requirements. The Economical Mode setting can improve scaling efficiency. For more information, see Use the Economical Mode feature to scale instances faster.
      Important
      • Your data stored on instances may be lost when the instances are reclaimed. To prevent data loss, do not store application data or logs in instances.
      • Stopped instances may be released due to the following reasons:
        • If the total number of instances in a scaling group exceeds the maximum number of instances allowed for the scaling group after you manually reduce the maximum number, Auto Scaling preferentially releases the ECS instances that are in the Stopped state.
        • If stopped instances fail to be added to a scaling group due to insufficient resources or overdue payments, the instances are released.
      • For more information about the Economical Mode feature, see the "Prerequisites", "Application resources", and "Trigger effects" sections in the Economical mode topic.
    VPC Select an existing VPC.
    Note When you create a scaling group that contains ECS instances created in the ECS console, the instance configurations and network type of the instances are automatically populated. We recommend that you use the default settings of these instances.
    vSwitch After you select a VPC, you must select one or more vSwitches. Each vSwitch resides in a single zone. To deploy instances across multiple zones, you must specify multiple vSwitches in different zones. We recommend that you select multiple zones to increase the success rate of scale-out.
    Note When you create a scaling group that contains ECS instances created in the ECS console, the instance configurations and network type of the instances are automatically populated. We recommend that you use the default settings of these instances.
    Add Existing Instance The Add Existing Instance parameter is available only if you set the Type parameter to ECS and set the Instance Configuration Source parameter to Launch Template or Select Existing Instance.

    If you specify an expected number of instances and then add instances to a scaling group, the expected number of instances for the scaling group automatically increases. For example, when you create a scaling group, you set the Expected Number of Instances parameter to 1 and add two existing instances to the scaling group. In this case, the expected number of instances increases to three.

    You can select Enable the scaling group to manage the instance lifecycle.
    • If the scaling group manages the lifecycles of the instances, Auto Scaling releases the instances after Auto Scaling considers the instances unhealthy and removes the instances from the scaling group or you manually remove the instances from the scaling group.
    • If the scaling group does not manage the lifecycles of the instances, Auto Scaling does not releases the instances after the instances are removed from the scaling group.
    Note You can add subscription instances to a scaling group. However, the lifecycles of the subscription instances cannot be managed by the scaling group.
    Associate CLB Instance After you associate a CLB instance with a scaling group, the instances that you add to the scaling group are automatically added as the backend servers of the CLB instance. Then, the CLB instance forwards requests to the instances.

    You can specify a server group to which you want to add instances. Valid values:

    • Default server group: the group of instances that are used to receive requests. If you do not specify a vServer group or a primary/secondary server group for a listener, requests are forwarded to the instances in the default server group.
    • vServer group: If you want to forward requests to backend servers that are not in the default server group or configure domain name- or URL-based routing methods, you can use vServer groups.

    If you specify the default server group and multiple vServer groups at the same time, the instances are added to these server groups.

    Note You can associate only a limited number of CLB instances and vServer groups with a scaling group. To view the quota or request a quota increase, go to Quota Center.
    Associate ALB Server Group The Associate ALB Server Group parameter is available only if you set the Network Type parameter to VPC. After you associate an ALB server group with a scaling group, the instances that you add to the scaling group are automatically added to the ALB server group to process requests that are forwarded by the ALB instance. You must specify the port number and weight for each backend server. By default, the weight of a backend server is 50. If you increase the weight of a server, the number of requests that are forwarded to the server increases. If you set the weight of a backend server to 0, no requests are forwarded to the server.

    If you associate multiple ALB server groups with the same scaling group, all instances that you add to the scaling group are added to the server groups.

    Note You can associate only a limited number of ALB server groups with a scaling group. To view the quota or request a quota increase, go to Quota Center.
    Associate ApsaraDB RDS Instance The Associate ApsaraDB RDS Instance parameter is available only if you set the Type parameter to ECS. After you associate an ApsaraDB RDS instance with a scaling group, the private IP addresses of the ECS instances that you add to the scaling group are automatically added to the whitelist that manages access to the ApsaraDB RDS instance. This way, the ECS instances and the ApsaraDB RDS instance can communicate with each other.
    Note You can associate only a limited number of ApsaraDB RDS instances with a scaling group. To view the quota or request a quota increase, go to Quota Center.
    Create Regular Rule When a scaling activity succeeds, fails, or is rejected, Auto Scaling sends notifications to you by using text messages, internal messages, or emails based on the rule. For more information, see Create a regular notification rule.
    Synchronize Alert Rule to CloudMonitor You can enable or disable this feature only when you create a scaling group. You cannot enable or disable this feature after a scaling group is created. After you enable this feature, the system automatically creates and associates a CloudMonitor application group with the scaling group. The alert rules of the scaling group are displayed in the CloudMonitor console in a synchronous manner.
  6. In the Create Scaling Group dialog box, click OK.
    You can view the scaling group on the Scaling Groups page. The scaling group is in the Disabled state. Scaling activities can be triggered only in scaling groups that are in the Enabled state. For more information, see Enable or disable scaling groups.

Enable or disable scaling groups

  • If a scaling group is in the Disabled state and the scaling group has a specified launch template or an active scaling configuration, you must enable the scaling group before scaling activities can be triggered in the scaling group.
  • If a scaling group is in the Enabled state and you do not need the scaling group, you can disable the scaling group. If a scaling activity is in progress when you disable the scaling group, the scaling activity continues until it is complete. Scaling requests that are made after the scaling group is disabled are rejected.
  1. Log on to the Auto Scaling console.
  2. In the left-side navigation pane, click Scaling Groups.
  3. In the top navigation bar, select a region.
  4. Enable or disable a scaling group.
    • Enable a scaling group: Find the scaling group that you want to enable and choose more > Enable in the Actions column. After you enable the scaling group, the scaling group enters the Enabled state.
    • Disable a scaling group: Find the scaling group that you want to disable and choose more > Disable in the Actions column. In the Disable Scaling Group message, click OK. After you disable the scaling group, the scaling group enters the Disabled state.

View or modify scaling groups

  • After you create a scaling group, you can view the basic information, instance list, scaling configuration source, scaling rules, and lifecycle hooks of the scaling group in the Auto Scaling console. This way, you can understand the basic configurations of the scaling group and basic information about the ECS instances or elastic container instances in the scaling group.
  • If your scaling group no longer meets your business requirements, you can simply modify one or more parameter settings of the scaling group. You do not need to create a new scaling group. Before you modify a scaling group, take note of the following items:
    Parameter Usage notes
    Minimum Number of Instances, Maximum Number of Instances, and Expected Number of Instances
    • If the number of ECS instances or elastic container instances falls outside the new range after you modify the settings of the Minimum Number of Instances parameter and the Maximum Number of Instances parameter, Auto Scaling adds instances to or removes instances from the scaling group until the number of instances is within the new range.
    • If you did not specify an expected number of instances for a scaling group when you created it and the number of instances drops below the minimum number of instances that is allowed after you modify the setting of the Minimum Number of Instances parameter, Auto Scaling triggers a scale-out activity to add instances to the scaling group until the number of instances is equal to the value of the Minimum Number of Instances parameter.
    • If you specified an expected number of instances for a scaling group when you created it and the number of instances does not match the new value of the Expected Number of Instances parameter after you modify the setting of the Expected Number of Instances parameter, Auto Scaling triggers a scaling activity to add or remove instances until the number of instances matches the value of the Expected Number of Instances parameter.
    Associate ApsaraDB RDS Instance If you want to modify the setting of the Associate ALB Server Group parameter for a scaling group that contains ECS instances, select When you associate RDS instances with or disassociate RDS instances from the scaling group, existing ECS instances in the scaling group are added to or removed from the whitelists of the RDS instances based on your business requirements.
    • If you select this option, Auto Scaling automatically adds the IP addresses of the existing ECS instances to the whitelist that manages access to the ApsaraDB RDS instance that you associate with the scaling group, or Auto Scaling automatically removes the IP addresses of the existing ECS instances from the whitelist that manages access to the ApsaraDB RDS instance that you disassociate from the scaling group.
    • If you do not select this option, the whitelist that manages access to the ApsaraDB RDS instance remains unchanged when you associate the ApsaraDB RDS instance with the scaling group or disassociate the ApsaraDB RDS instance from the scaling group.
    Associate CLB Instance and Associate ALB Server Group If you want to modify the settings of the Associate CLB Instance and Associate ALB Server Group parameters for a scaling group that contains ECS instances or elastic container instances, select When you associate SLB instances with or disassociate SLB instances from the scaling group, existing instances in the scaling group are added to or removed from the server groups of the SLB instances based on your business requirements.
    • If you select this option, Auto Scaling automatically adds the existing ECS instances or elastic container instances to the backend server groups of the CLB instances or ALB server groups that you associate with the scaling group, or Auto Scaling automatically removes the existing ECS instances or elastic container instances from the backend server groups of the CLB instances or ALB server groups that you disassociate from the scaling group.
    • If you do not select this option, the number of the backend servers remains unchanged after you associate the CLB instances or ALB server groups with your scaling group or disassociate the CLB instances or ALB server groups from your scaling group.
  1. Log on to the Auto Scaling console.
  2. In the left-side navigation pane, click Scaling Groups.
  3. In the top navigation bar, select a region.
  4. View or modify a scaling group.
    Action Procedure
    View a scaling group
    1. On the Scaling Groups page, find the scaling group whose information that you want to view.
      The page displays the following information about the scaling group: the scaling group name/ID, type, status, instance configuration source, and network configurations.
      Note If an exception occurs on the scaling group, the Move icon icon appears in the Status column. You can move the pointer over the icon to view the error message and identify and troubleshoot the error.
    2. Find the scaling group and click Details in the Actions column.
    3. In the upper part of the page that appears, specify the tabs to view the details of the scaling group.

      You can view the basic information, instance configuration source, instance list, monitoring information, scaling rules, scaling activities, lifecycle hooks, notifications, and rolling updates of the scaling group.

    Modify a scaling group
    1. On the Scaling Groups page, find the scaling group that you want to modify and click Edit in the Actions column.
    2. Modify the parameter settings of the scaling group.

      For information about the parameters of a scaling group, see Manage scaling groups.

    3. Click OK.

Delete scaling groups

  • If the deletion protection feature is enabled for a scaling group, you cannot delete the scaling group by using the Auto Scaling console or by calling API operations. The deletion protection helps prevent misdeletion of scaling groups.
  • If you no longer require a scaling group for which deletion protection is not enabled, you can delete the scaling group to free up the scaling group quota. After you delete a scaling group, the scaling configurations and scaling rules of the scaling group are also deleted. If the scaling group that you want to delete contains ECS instances or elastic container instances that are in the In Service state, Auto Scaling stops the instances and then removes the manually added instances from the scaling group or releases the automatically created instances before the scaling group is deleted.
    Note Before you delete a scaling group, make sure that the deletion protection feature is disabled for the scaling group. If the deletion protection feature is enabled for the scaling group, disable the deletion protection feature before you delete the scaling group.
  1. Log on to the Auto Scaling console.
  2. In the left-side navigation pane, click Scaling Groups.
  3. In the top navigation bar, select a region.
  4. Find the scaling group that you want to delete and choose menu > Set Deletion Protection in the Actions column.
  5. In the dialog box that appears, check whether the deletion protection feature is enabled.
    • If the deletion protection feature is enabled, disable the feature and click OK.
    • If the deletion protection feature is disabled, click OK.
  6. Find the scaling group that you want to delete and click Delete in the Actions column.
  7. In the Delete Scaling Group message, click OK.
    The scaling group enters the Deleting state. After the scaling group is deleted, it is no longer displayed on the Scaling Groups page.