deleteVpcPeeringInstance

Available in VPC

Delete a VPC peering instance by specifying the VPC peering instance number.

Syntax

The deleteVpcPeeringInstance syntax is as follows:

./ncloud vpc deleteVpcPeeringInstance \
    --vpcPeeringInstanceNo <vpc-peering-instance-no> \
    [--regionCode <KR|SGN|JPN>] \
    [--output <json|xml>]

Options

This section describes the options available when running deleteVpcPeeringInstance.

Required options

The following options are required for deleteVpcPeeringInstance.

Common options

For information about the options common to all vpc subcommands, see VPC options.

Examples

If the request to delete a VPC peering instance is successful, the instance's configuration information and termination status are returned.

Command

The command example is as follows:

./ncloud vpc deleteVpcPeeringInstance \
    --vpcPeeringInstanceNo 67890123 \
    --regionCode KR \
    --output json

Output

The output example is as follows:

{
  "deleteVpcPeeringInstanceResponse": {
    "totalRows": 1,
    "vpcPeeringInstanceList": [
      {
        "vpcPeeringInstanceNo": "67890123",
        "vpcPeeringName": "test-peering",
        "regionCode": "KR",
        "createDate": "2026-07-07T16:41:47+0900",
        "lastModifyDate": "2026-07-07T16:41:47+0900",
        "vpcPeeringInstanceStatus": {
          "code": "RUN",
          "codeName": "In operation"
        },
        "vpcPeeringInstanceStatusName": "Terminating",
        "vpcPeeringInstanceOperation": {
          "code": "TERMT",
          "codeName": "TERMINATE OP"
        },
        "sourceVpcNo": "12345678",
        "sourceVpcName": "test-vpc-01",
        "sourceVpcIpv4CidrBlock": "10.0.0.0/16",
        "sourceVpcLoginId": "user@example.com",
        "targetVpcNo": "12345679",
        "targetVpcName": "test-vpc-02",
        "targetVpcIpv4CidrBlock": "172.31.0.0/16",
        "targetVpcLoginId": "user2@example.com",
        "vpcPeeringDescription": "Updated peering description",
        "hasReverseVpcPeering": false,
        "isBetweenAccounts": true,
        "reverseVpcPeeringInstanceNo": ""
      }
    ],
    "requestId": "f6a7b8c9-d0e1-2345-fabc-678901234567",
    "returnCode": "0",
    "returnMessage": "success"
  }
}