getVpcPeeringInstanceDetail

Available in VPC

Get VPC peering instance details by specifying the VPC peering instance number.

Syntax

The getVpcPeeringInstanceDetail syntax is as follows:

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

Options

This section describes the options available when running getVpcPeeringInstanceDetail.

Required options

The following options are required for getVpcPeeringInstanceDetail.

Common options

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

Examples

If the request to retrieve VPC peering instance details is successful, the instance's configuration information is returned.

Command

The command example is as follows:

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

Output

The output example is as follows:

{
  "getVpcPeeringInstanceDetailResponse": {
    "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": "Running",
        "vpcPeeringInstanceOperation": {
          "code": "NULL",
          "codeName": "NULL 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": "VPC peering example",
        "hasReverseVpcPeering": false,
        "isBetweenAccounts": true,
        "reverseVpcPeeringInstanceNo": ""
      }
    ],
    "requestId": "c3d4e5f6-a7b8-9012-cdef-345678901234",
    "returnCode": "0",
    "returnMessage": "success"
  }
}