createVpcPeeringInstance
- Print
- PDF
createVpcPeeringInstance
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Can be used in a VPC environment.
Overview
This creates a VPC Peering instance through the Peering requests.
Request
Request parameters
| Parameter name | Required | Type | Restrictions | Description |
|---|---|---|---|---|
| regionCode | No | String | Region code You can decide the region in which a VPC Peering instance will be created. regionCode can be obtained through the getRegionList action. Default: Select the first region of the getRegionList search results | |
| vpcPeeringName | No | String | Min : 3, Max : 30 Only lower case characters, numbers, and special character (-) are allowed, and it has to start with an English letter. It must end with an English letter or number. | The name of the VPC Peering to be created Default: NAVER Cloud Platform automatically grants it. |
| sourceVpcNo | Yes | String | The number of VPC that sends requests sourceVpcNo can be obtained through the getVpcList action. | |
| targetVpcNo | Yes | String | The number of the VPC that receives requests targetVpcNo can be obtained through the getVpcList action in the account that receives requests. If the IPv4 CIDR blocks of the VPC sending the request and the receiving VPC overlap, then you can't connect with VPC Peering. | |
| targetVpcName | Conditional | String | The name of the VPC that receives requests If the account receiving the request is different from the sending account, then you must enter the name of the VPC receiving the request. | |
| targetVpcLoginId | Conditional | String | Owner ID of the VPC that receives requests If the account receiving the request is different from the sending account, then you must enter the account. It must coincide with the email format. | |
| vpcPeeringDescription | No | String | Min : 0, Max : 1000 Bytes | The description about the VPC Peering instance to be created |
| responseFormatType | No | String | Format type of the response results Options : xml | json Default : xml |
Response
Response body
Example
Request Example
GET {API_URL}/vpc/v2/createVpcPeeringInstance
?regionCode=KR
&vpcPeeringName=test-***
&sourceVpcNo=***05
&targetVpcNo=***06
Response Example
<createVpcPeeringInstanceResponse>
<requestId>450c98e2-dca5-46f7-9f35-5ec1a1728213</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<vpcPeeringInstanceList>
<vpcPeeringInstance>
<vpcPeeringInstanceNo>***6212</vpcPeeringInstanceNo>
<vpcPeeringName>test-***</vpcPeeringName>
<regionCode>KR</regionCode>
<createDate>2020-08-07T17:53:06+0900</createDate>
<vpcPeeringInstanceStatus>
<code>INIT</code>
<codeName>init</codeName>
</vpcPeeringInstanceStatus>
<vpcPeeringInstanceStatusName>Waiting</vpcPeeringInstanceStatusName>
<vpcPeeringInstanceOperation>
<code>NULL</code>
<codeName>NULL OP</codeName>
</vpcPeeringInstanceOperation>
<sourceVpcNo>***05</sourceVpcNo>
<sourceVpcName>test-***</sourceVpcName>
<sourceVpcIpv4CidrBlock>***.**1.0.0/16</sourceVpcIpv4CidrBlock>
<sourceVpcLoginId>test-***@naver.com</sourceVpcLoginId>
<targetVpcNo>***06</targetVpcNo>
<targetVpcName>test-***</targetVpcName>
<targetVpcIpv4CidrBlock>***.**2.0.0/16</targetVpcIpv4CidrBlock>
<targetVpcLoginId>test-***@naver.com</targetVpcLoginId>
<vpcPeeringDescription></vpcPeeringDescription>
<hasReverseVpcPeering>false</hasReverseVpcPeering>
<isBetweenAccounts>false</isBetweenAccounts>
<reverseVpcPeeringInstanceNo></reverseVpcPeeringInstanceNo>
</vpcPeeringInstance>
</vpcPeeringInstanceList>
</createVpcPeeringInstanceResponse>
Was this article helpful?