All Products
Search

This Product

    Virtual Private Cloud:ModifyExpressConnectTrafficQos

    Document Center

    Virtual Private Cloud:ModifyExpressConnectTrafficQos

    Last Updated:Aug 29, 2024

    Modifies a quality of service (QoS) policy or associates a QoS policy with a dedicated Express Connect circuit.

    Debugging

    OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

    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.
    OperationAccess levelResource typeCondition keyAssociated operation
    vpc:ModifyExpressConnectTrafficQosupdate
    • All Resources
      *
      none
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    RegionIdstringYes

    The region ID of the resource.

    You can call the DescribeRegions operation to query the most recent region list.

    		cn-shanghai
    ClientTokenstringYes

    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 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
    QosNamestringNo

    The name of the QoS policy.

    		qos-test
    QosDescriptionstringNo

    The description of the QoS policy.

    		qos-test
    QosIdstringYes

    The ID of the QoS policy.

    		qos-2giu0a6vd5x0mv4700
    AddInstanceListarray<object>No

    The instances to be added. Ignore this parameter if no instances are to be added.

    objectNo
    InstanceIdstringNo

    The ID of the instance to be associated.

    		pc-bp159zj8zujwy3p07****
    InstanceTypestringNo

    The type of instance to be associated. Set the value to PHYSICALCONNECTION.

    		PHYSICALCONNECTION
    RemoveInstanceListarray<object>No

    The instances to be removed. Ignore this parameter if no instances are to be removed.

    objectNo
    InstanceIdstringNo

    The ID of the associated instance.

    		pc-bp1j37am632492qzw****
    InstanceTypestringNo

    The type of the associated instance. Set the value to PHYSICALCONNECTION.

    		PHYSICALCONNECTION

    Response parameters

    ParameterTypeDescriptionExample
    object
    RequestIdstring

    The request ID.

    		54B48E3D-DF70-471B-AA93-08E683A1B457

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "54B48E3D-DF70-471B-AA93-08E683A1B457"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400IllegalParam.%sThe param of %s is illegal.The parameter is invalid.
    400IncorrectStatus.QosThe status of QoS is incorrect.The status of the QoS policy is abnormal and the operation cannot be performed. Try again later.
    400IncorrectStatus.PconnIdListThe status of PconnIdList is incorrect.This operation cannot be performed because the current physical connection is in an abnormal state.
    400ResourceAlreadyAssociated.PconnQosThe specified resource of PconnQos is already associated.The physical line has been bound to another QoS policy.
    400EcQoSConflictThe specified QoS is conflict with other QoS.The current QoS configuration conflicts with other configurations. Please try again later.
    400IncorrectBusinessStatus.PconnIdListThe business status of PconnIdList is incorrect.This operation cannot be performed because the current physical line is in arrears.
    400EcPconnWithVpconnNotAllowAssociateQoSThe specified Pconn with Vpconn is not allowed to associate with Qos.Exclusive physical lines that contain shared physical lines cannot be bound to QoS policies.
    400EcPconnWithCrossAccountVbrNotAllowAssociateQoSThe specified Pconn with cross account VBR is not allowed to associate with Qos.Exclusive physical connections that contain cross-account virtual border routers cannot bind QoS policies.
    400EcDeviceNotSupportQoSThe specified Pconn is on the device which is not supported QoS.The device where the physical connection is located does not support the QoS feature.
    400EcPconnVbrMustContainsAllIn the single VBR with multiple Pconn scene, all Pconn must be associated with the same Qos.In a single VBR and multiple Pconn scenarios, all Pconn must be bound to a QoS policy.

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

    Change history

    Change timeSummary of changesOperation
    2024-03-29The Error code has changed. The request parameters of the API has changedView Change Details