Updates the Autoscaler configurations of a service.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
eas:UpdateServiceAutoScaler | update | *Service acs:eas:{#regionId}:{#accountId}:service/{#ServiceName} |
| none |
Request syntax
PUT /api/v2/services/{ClusterId}/{ServiceName}/autoscaler HTTP/1.1
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ClusterId | string | Yes | The region ID of the service. | cn-shanghai |
ServiceName | string | Yes | The service name. For more information about how to query the service name, see ListServices . | foo |
body | object | No | The request body. | |
min | integer | Yes | The minimum number of instances. The value must be greater than 0. | 2 |
max | integer | Yes | The maximum number of instances. The value must be greater than that of the min parameter. | 8 |
scaleStrategies | array<object> | Yes | The auto scaling policies. | |
object | No | |||
metricName | string | Yes | The name of the metric for triggering auto scaling. Valid values:
| qps |
threshold | float | Yes | The threshold of the metric that triggers auto scaling.
| 100 |
service | string | No | The service for which the metric is specified. If you do not set this parameter, the current service is specified by default. | demo_svc |
behavior | object | No | The Autoscaler operation. | |
scaleUp | object | No | The scale-out operation. | |
stabilizationWindowSeconds | integer | No | The time window that is required before the scale-out operation is performed. Default value: 0. The scale-out operation can be performed only if the specified metric exceeds the specified threshold in the specified time window. | 0 |
scaleDown | object | No | The scale-in operation. | |
stabilizationWindowSeconds | integer | No | The time window that is required before the scale-in operation is performed. Default value: 300. The scale-in operation can be performed only if the specified metric drops below the threshold in the specified time window. | 300 |
onZero | object | No | The operation that reduces the number of instances to 0. | |
scaleDownGracePeriodSeconds | integer | No | The time window that is required before the number of instances is reduced to 0. Default value: 600. The number of instances can be reduced to 0 only if no request is available or no traffic exists in the specified time window. | 600 |
scaleUpActivationReplicas | integer | No | The number of instances that you want to create at a time if the number of instances is scaled out from 0. Default value: 1. | 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "40325405-579C-4D82****",
"Message": "Update auto scale for service [foo] successfully"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-05-17 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2022-09-16 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2022-09-16 | The internal configuration of the API is changed, but the call is not affected | View Change Details |