Deletes a connection over an Express Connect circuit.
Operation description
You can only delete a connection over an Express Connect circuit that is in the Rejected, Canceled, AllocationFailed, or Terminated state.
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 |
---|---|---|---|---|
vpc:DeletePhysicalConnection | delete |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The region ID of the Express Connect circuit. You can call the DescribeRegions operation to query the most recent region list. | cn-shanghai |
PhysicalConnectionId | string | Yes | The ID of the Express Connect circuit. | pc-119mfjzm7********* |
ClientToken | string | No | 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 and cannot exceed 64 characters in length. | 02fb3da4-130e-11e9-8e44-0016e04115b |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidPhysicalConnectionId.NotMatched | instance id not matched. | The instance ID does not match. |
400 | Forbidden.VBRExists | physical connection owner's vbr still exists. | The VBR of the Express Connect circuit still exists. |
400 | Forbidden.VBRExists | vbr owner's vbr still exists. | The VBR still exists. |
400 | Forbidden.AssociateToVBR | The physical connection still associate to VBR. | The physical connection has configured a virtual border router. |
400 | OperationDenied.NeedVpconnOwner | The operation is denied. | The deletion failed. Only the owner of a shared port can delete it. |
400 | OperationDenied.NeedPconnOwner | The operation is denied. | The deletion failed. Only the owner of a physical port can delete it. |
400 | Forbidden.VBRExists | The vbr still exists. | The VBR still exists and the port cannot be deleted. |
400 | Forbidden.NotInAllowDeleteStatus | Only physical connection in the Cancelled, Rejected, Terminated, Allocated, or AllocationFailed states can be deleted. | Only physical connection in the Cancelled, Rejected, Terminated, Allocated, or AllocationFailed states can be deleted. |
400 | ResourceAlreadyAssociated.PconnQos | The specified resource of PconnQos is already associated. | The physical line has been bound to another QoS policy. |
400 | ResourceNotFound.PhysicalConnectionId | PhysicalConnection is not found. | PhysicalConnectionId is set to an invalid value. |
404 | InvalidPhysicalConnectionId.NotFound | The PhysicalConnectionId provided does not exist in our records. | The Express Connect circuit does not exist. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-06-13 | The Error code has changed | View Change Details |
2024-02-01 | The Error code has changed | View Change Details |
2023-11-28 | API Description Update. The Error code has changed | View Change Details |