setVpcPeeringDescription
- Print
- PDF
setVpcPeeringDescription
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Can be used in a VPC environment.
Overview
This modifies the description about the VPC Peering instance.
Request
Request parameters
| Parameter name | Required | Type | Restrictions | Description |
|---|---|---|---|---|
| regionCode | No | String | Region code You can decide the region of VPC Peering instance whose description will be modified. regionCode can be obtained through the getRegionList action. Default: Select the first region of the getRegionList search results | |
| vpcPeeringInstanceNo | Yes | String | The number of VPC Peering instance whose description will be modified vpcPeeringInstanceNo can be obtained through the getVpcPeeringInstanceList action. | |
| vpcPeeringDescription | No | String | Min : 0, Max : 1000 Bytes | The description about a VPC Peering instance to be modified |
| 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/setVpcPeeringDescription
?regionCode=KR
&vpcPeeringInstanceNo=***6212
&vpcPeeringDescription=test-description
Response Example
<setVpcPeeringDescriptionResponse>
<requestId>714c5071-50d0-48ea-8e4f-e449009036d2</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<vpcPeeringInstanceList>
<vpcPeeringInstance>
<vpcPeeringInstanceNo>***6212</vpcPeeringInstanceNo>
<vpcPeeringName>test-***</vpcPeeringName>
<regionCode>KR</regionCode>
<createDate>2020-08-04T14:57:08+0900</createDate>
<vpcPeeringInstanceStatus>
<code>RUN</code>
<codeName>run</codeName>
</vpcPeeringInstanceStatus>
<vpcPeeringInstanceStatusName>Running</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>test-description</vpcPeeringDescription>
<hasReverseVpcPeering>false</hasReverseVpcPeering>
<isBetweenAccounts>false</isBetweenAccounts>
<reverseVpcPeeringInstanceNo></reverseVpcPeeringInstanceNo>
</vpcPeeringInstance>
</vpcPeeringInstanceList>
</setVpcPeeringDescriptionResponse>
Was this article helpful?