All Products
Document Center

Virtual Private Cloud:DeleteVpnAttachment

Last Updated:Dec 06, 2023

Deletes an IPsec-VPN connection.

Operation Description

  • If the IPsec-VPN connection is associated with a transit router, you must first disassociate the IPsec-VPN connection from the transit router before you delete the IPsec-VPN connection.
  • If the IPsec-VPN connection is not associated with a resource, you can call the DeleteVpnAttachment to delete the IPsec-VPN connection.


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.


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
  • VpnConnections

Request parameters


The ID of the region where the IPsec-VPN connection is established.

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


The ID of the IPsec-VPN connection.


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.

Response parameters


The response parameters.


The request ID.


The status code returned by the current operation. 200 indicates that the operation is successful.


Indicates whether the current operation is successful.

  • true
  • false

The information returned by the current operation.



Sample success responses


  "RequestId": "29440C49-398F-3D06-BA8B-E3CD13F3246D",
  "Code": "200",
  "Success": true,
  "Message": "successful"

Error codes

HTTP status codeError codeError messageDescription
400VpnConnection.ConfiguringThe specified service is configuring.The service is being configured. Try again later.
400InternalErrorThe request processing has failed due to some unknown error, exception or failure.An internal error occurred.
403Forbbiden.SubUserUser not authorized to operate on the specified resource as your account is created by another user. -
403Forbidden User not authorized to operate on the specified resource. -
404InvalidVpnConnectionInstanceId.NotFound The specified vpn connection instance id does not exist. -

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

Change history

Change timeSummary of changesOperation
No change history