Modifies a quality of service (QoS) queue.
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 Resourcesis 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 |
|---|---|---|---|---|
| vpc:ModifyExpressConnectTrafficQosQueue | update |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The region ID of the QoS policy. You can call the DescribeRegions operation to query the most recent region list. | cn-shanghai |
| ClientToken | string | Yes | The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must ensure that the value is unique among all requests. The client token can contain only ASCII characters. Note
If you do not set this parameter, the system uses RequestId as ClientToken. RequestId might be different for each API request.
| 123e4567-e89b-12d3-a456-426655440000 |
| QueueName | string | No | The name of the QoS queue. The name must be 0 to 128 characters in length and cannot start with | qos-queue-test |
| QueueDescription | string | No | The description of the QoS queue. The description must be 0 to 256 characters in length and cannot start with | qos-queue-test |
| QosId | string | Yes | The ID of the QoS policy. | qos-2giu0a6vd5x0mv4700 |
| QueueId | string | Yes | The ID of the QoS queue. | qos-queue-9nyx2u7n71s2rcy4n5 |
| BandwidthPercent | string | No | The percentage of bandwidth allocated to the QoS queue.
| 100 |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "079874CD-AEC1-43E6-AC03-ADD96B6E4907"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | IllegalParam.%s | The param of %s is illegal. | The parameter is invalid. |
| 400 | IncorrectStatus.Qos | The status of QoS is incorrect. | The status of the QoS policy is abnormal and the operation cannot be performed. Try again later. |
| 400 | EcQoSConflict | The specified QoS is conflict with other QoS. | The current QoS configuration conflicts with other configurations. Please try again later. |
| 400 | QuotaExceeded.QosMediumPriorityQueueBandwidthPercent | The quota of QosMediumPriorityQueueBandwidthPercent is exceeded. | The sum of the bandwidth percentages of the normal priority queues in the QoS policy exceeds the specification. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|