All Products
Search
Document Center

Auto Scaling:CompleteLifecycleAction

Last Updated:Oct 26, 2026

Ends the wait state of a scaling activity in advance.

Operation description

Operation description

Allows you to set the next action after the wait state ends. You can set the action to continue the scaling activity (CONTINUE), abandon the scaling activity (ABANDON), or perform a rollback (ROLLBACK).

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:CompleteLifecycleAction

update

*ScalingGroup

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

None None

Request parameters

Parameter

Type

Required

Description

Example

LifecycleHookId

string

Yes

The ID of the lifecycle hook.

ash-bp14g3ee6bt3sc98****

LifecycleActionToken

string

Yes

The identifier of the wait state of the scaling activity. You can obtain this value from the Message Service (MNS) queue or MNS topic specified by the lifecycle hook.

aaaa-bbbbb-cccc-ddddd

LifecycleActionResult

string

No

The next action after the wait state of the lifecycle hook ends. Valid values:

  • CONTINUE: Continues to respond to the scale-out activity and adds the ECS instance to the scaling group, or continues to respond to the scale-down activity and removes the ECS instance from the scaling group.

  • ABANDON: Terminates the scale-out activity and directly releases the created ECS instance, or continues to respond to the scale-down activity and removes the ECS instance from the scaling group.

  • ROLLBACK: Rejects the release of the ECS instance and performs a rollback for a scale-down activity. For a scale-out activity, the effect is the same as that of ABANDON.

If you do not specify this parameter, the next action after the wait state of the lifecycle hook ends remains the DefaultResult value configured for the lifecycle hook.

When multiple lifecycle hooks in a scaling group are triggered synchronously, the final next action is determined as follows:

  • For a scale-down activity, when the wait state triggered by an ABANDON or ROLLBACK lifecycle hook ends, the wait states of subsequent lifecycle hooks end in advance.

  • When a CONTINUE lifecycle hook suspends a scale-down activity, or for a scale-out activity, subsequent lifecycle hooks continue to suspend the scaling activity until the wait state triggered by the last lifecycle hook ends. The final next action is determined by the type of the last lifecycle hook that ends the wait state.

CONTINUE

ClientToken

string

No

Ensures the idempotence of the request.

You can generate a parameter value on your client to ensure that the value is unique across different requests. The value can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How to ensure idempotence.

123e4567-e89b-12d3-a456-42665544****

RegionId

string

No

The ID of the region to which the scaling group belongs.

cn-qingdao

Response elements

Element

Type

Description

Example

object

RequestId

string

The request ID.

473469C7-AA6F-4DC5-B3DB-A3DC0DE3****

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.