When a scaling activity succeeds, fails, or is rejected, Auto Scaling can send notifications through SMS messages and emails. You must handle the related events after receiving the notifications. You can call the DescribeAlertConfiguration operation to query the status of scaling activities for which SMS and email notifications are sent in a scaling group. This helps you stay informed about changes to scaling activities and respond quickly to improve scaling efficiency.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
ess:DescribeAlertConfiguration |
get |
*ScalingGroup
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ScalingGroupId |
string |
Yes |
The ID of the scaling group. |
asg-bp18p2yfxow2dloq**** |
| RegionId |
string |
Yes |
The ID of the region where the scaling group resides. |
cn-hangzhou |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
473469C7-AA6F-4DC5-B3DB-A3DC0DE3**** |
| ScaleStatuses |
object |
||
| ScaleStatus |
array |
The status of scaling activities for which SMS messages, internal messages, and email notifications are sent in the scaling group. |
|
|
string |
The status of scaling activities for which SMS, internal message, and email notifications are sent in the scaling group. Valid values:
|
ScaleSuccessful |
Examples
Success response
JSON format
{
"RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3****",
"ScaleStatuses": {
"ScaleStatus": [
"ScaleSuccessful"
]
}
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.