Calls the DeleteTransitRouterVpcAttachment operation to delete a virtual private cloud (VPC) connection from an Enterprise Edition transit router.
Operation description
DeleteTransitRouterVpcAttachment is an asynchronous operation. After you send a request, the system returns a RequestId but the VPC connection is not yet deleted. The deletion task continues to run in the background. You can call ListTransitRouterVpcAttachments to query the status of the VPC connection.
If the VPC connection is in the Detaching state, the VPC connection is being deleted. In this state, you can only query the VPC connection. You cannot perform other operations on the VPC connection.
If the VPC connection cannot be found, the VPC connection is deleted.
When you call DeleteTransitRouterVpcAttachment, make sure that the parameter values you specify are valid. If you specify invalid parameter values, the system still returns a RequestId but does not delete the VPC connection from the Enterprise Edition transit router.
Before you begin
Before you delete a VPC connection, make sure that you have not configured a routing rule to access PrivateZone by using the VPC-connected instance. To delete the routing rule to PrivateZone, see UnroutePrivateZoneInCenToVpc.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
cen:DeleteTransitRouterVpcAttachment |
delete |
*TransitRouterVpcAttachment
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| 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 client token can contain only ASCII characters. Note
If you do not specify this parameter, the system automatically uses the RequestId of the API request as the ClientToken. The RequestId may be different for each API request. |
02fb3da4-130e-11e9-8e44-001**** |
| TransitRouterAttachmentId |
string |
Yes |
The ID of the VPC connection. |
tr-attach-ia340z7xis7t5s**** |
| DryRun |
boolean |
No |
Specifies whether to perform a dry run, including permission and instance status verification. Valid values:
|
false |
| Force |
boolean |
No |
Specifies whether to force delete the VPC connection. Valid values:
|
false |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response. |
||
| RequestId |
string |
The request ID. |
7E61D334-4025-41EF-9145-FC327B35301D |
Examples
Success response
JSON format
{
"RequestId": "7E61D334-4025-41EF-9145-FC327B35301D"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | OperationFailed.AttachmentReferencedVpcRouteEntryExisted | Operation is failed because there is at least one route entry which next hop is the specified attachment. | The error message returned because this operation is not supported when a route points to an attachment. |
| 400 | OperationFailed.RouteTablePropagationExist | The specified TransitRouterAttachment has configured RouteTablePropagation. Please remove the configuration first. | The error message returned because you cannot perform the operation when a route learning correlation is configured for the network instance connection. Disassociate from the route learning correlation and try again. |
| 400 | OperationFailed.MulticastDomainAssociationExist | The specified TransitRouterAttachment has configured MulticastDomainAssociation. Please remove the configuration first. | The error message returned because the specified transit router attachment (TransitRouterAttachment) is added to a multicast domain. Remove the attachment from the multicast domain and try again. |
| 400 | OperationUnsupported.TransitRouterType | The specified TransitRouterType does not support the operation. | The error message returned because this operation is not supported by the specified type of transit router. |
| 400 | OperationFailed.PrefixListExist | Operation failed because PrefixList exists. | The error message returned because a prefix list exists. |
| 400 | InvalidTransitRouterAttachmentId.NotFound | TransitRouterAttachmentId is not found. | The error message returned because the ID of the network instance does not exist. |
| 400 | IncorrectStatus.VpcRouteEntry | The resource is not in a valid state for the attachment operation. | The error message returned because the status of the VPC route entry does not support this operation. Try again later. |
| 400 | IncorrectStatus.VpcSwitch | The resource is not in a valid state for the attachment operation. | The error message returned because the status of the vSwitch does not support this operation. Try again later. |
| 400 | IncorrectStatus.Vpc | The resource is not in a valid state for the operation. | The error message returned because the status of the VPC does not support this operation. Try again later. |
| 400 | OperationFailed.NotSupportForceDelete | Not support force delete attachment. | The error message returned because the specified resource cannot be forcefully deleted. |
| 400 | IncorrectStatus.VpcRouteTable | The VPC route table is not in a desired state. | The error message returned because the VPC route table is in an unstable state. Try again later. |
| 400 | OperationFailed.RouteEntryExist | Failed to delete the instance because a route table entry points to the instance. | Failed to delete the instance because one or more routes point to the instance. Delete the routes and try again. |
| 400 | OperationFailed.RouteTableAssociationExist | Operation failed because there is associated routing table. | The network connection deletion failed because there is an associated routing table. |
| 400 | IncorrectStatus.VpcResource | The resource is not in a valid state for the attachment operation. | The error message returned because this operation is not supported when the specified VPC is in an unstable state. Wait until all operations related to the VPC are completed. |
| 400 | OperationFailed.FlowLogExistOrNisOpened | Operation failed because FlowLog exists or Nis opened. | The error message returned because this operation is not supported when a flow log exists or the NIS service is activated. |
| 400 | InvalidParameter | Invalid parameter. | The error message returned because the parameter is set to an invalid value. |
| 400 | Unauthorized | The AccessKeyId is unauthorized. | The error message returned because you do not have the permissions to perform this operation. |
| 400 | OperationNotPermitted.AttachmentManagedByCloudService | The specified Attachment managed by cloud service can only be deleted through cloud service. | |
| 400 | InvalidParameter.TransitRouterAttachmentId | The specified parameter TransitRouterAttachmentId is invalid. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.