Puts Elastic Compute Service (ECS) instances into the Protected state. When ECS instances are put into the Protected state, they become immune to manual deletion attempts by using the Auto Scaling console or API operations. This operation serves as a robust safeguard, efficiently preventing any inadvertent instance release that could lead to irreversible consequences.
Operation description
Once ECS instances enter the Protected state, they become subject to the following restrictions:
- ECS instances will persist in the Protected state, unless you deliberately remove them from this state.
- Even in scenarios where automatic scale-in actions are initiated due to fluctuations in the number of ECS instances or the execution of event-triggered tasks, Auto Scaling does not remove ECS instances that are in the Protected state from their respective scaling groups. Only after being manually removed from their respective scaling groups can ECS instances that are in the Protected state be released. For more information, see Remove an ECS instance.
- ECS instances in the Protected state maintain their existing health status even when they undergo stopping or restarting processes.
Debugging
Authorization information
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ScalingGroupId | string | Yes | The ID of the scaling group. | asg-bp18p2yfxow2dloq**** |
| ProtectedFromScaleIn | boolean | Yes | Specifies whether to protect ECS instances from being stopped or removed from the scaling group during scale-ins. Valid values:
| true |
| InstanceIds | array | Yes | The IDs of the ECS instances. | |
| string | Yes | The IDs of the ECS instances. | i-28wt4**** |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3****"
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|