DeleteExpressConnectTrafficQosQueue - Virtual Private Cloud

Deletes a quality of service (QoS) queue.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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
vpc:DeleteExpressConnectTrafficQosQueue	delete	All Resources ``	none	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 token, but you must make sure that the token is unique among different requests. The client token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.	0c593ea1-3bea-11e9-b96b-88e9fe637760
QosId	string	Yes	The ID of the QoS policy.	qos-2giu0a6vd5x0mv4700
QueueId	string	Yes	The ID of the QoS queue.	qos-queue-9nyx2u7n71s2rcy4n5

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The ID of the request.	9B9300FE-11E2-4E3B-949C-BED3B44DD26D

Examples

Sample success responses

JSONformat

{
  "RequestId": "9B9300FE-11E2-4E3B-949C-BED3B44DD26D"
}

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.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-03-29	The Error code has changed	View Change Details