All Products
Search
Document Center

Auto Scaling:DeleteScalingGroup

Last Updated:Sep 10, 2026

Deletes a scaling group.

Operation description

Operation description

Take note of the following items when you delete a scaling group:

  • Deleting a scaling group also deletes the associated scaling configurations, scaling rules, scaling activities, and scaling requests.

  • Deleting a scaling group does not delete scheduled nodes, CloudMonitor event-triggered tasks, load balancing instances, or ApsaraDB RDS instances.

  • If you enabled the Enable Scaling Group Protection feature when you created the scaling group, you cannot delete the scaling group in the console or by calling an API operation. This effectively prevents accidental deletion of the scaling group.

  • If you enabled the Instance Release Protection feature when you created ECS instances and then added the instances to a scaling group for management, manually added ECS instances are forcibly removed from the scaling group and automatically created ECS instances are automatically released together with the scaling group when you delete the scaling group.

    Note

    Before you delete a scaling group, to prevent ECS instances in the scaling group from being forcibly released, you must enable the protection feature for ECS instances in the scaling group even if you have separately enabled instance release protection for the ECS instances. This ensures that the instances are not forcibly released when the scaling group is deleted. For more information, see SetInstancesProtection.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

ess:DeleteScalingGroup

delete

*ScalingGroup

acs:ess:{#regionId}:{#accountId}:scalinggroup/{#ScalingGroupId}

None None

Request parameters

Parameter

Type

Required

Description

Example

ScalingGroupId

string

Yes

The ID of the scaling group.

asg-bp18p2yfxow2dloq****

ForceDelete

boolean

No

Specifies whether to force delete the scaling group and remove and release ECS instances or elastic container instances if the scaling group contains ECS instances or elastic container instances, or if a scaling activity is in progress. Valid values:

  • true: Force deletes the scaling group. The scaling group is first stopped and new scaling activity requests are rejected. After existing scaling activities are complete, all ECS instances and elastic container instances in the scaling group are removed from the scaling group. Manually added ECS instances and elastic container instances are removed, and ECS instances and elastic container instances that are automatically created by Auto Scaling are deleted. Then, the scaling group is deleted.

  • false: Does not force delete the scaling group. The scaling group is stopped and then deleted if the following conditions are met:

    • No scaling activity is being executed in the scaling group.

    • The current number of ECS instances or elastic container instances (Total Capacity) in the scaling group is 0.

Default value: false.

false

RegionId

string

No

The region ID of the scaling group.

cn-qingdao

Response elements

Element

Type

Description

Example

object

RequestId

string

The request ID.

473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E

Examples

Success response

JSON format

{
  "RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3****"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.