Accepting a VPC Peering Connection Request
Function
This API is used to accept a VPC peering connection request. Use the following method to send a request to the endpoint of the peer VPC:
PUT https://VPC endpoint/v2.0/vpc/peerings/{peering_id}/accept
For details about the VPC endpoint, see Regions and Endpoints.
URI
- URI format
PUT /v2.0/vpc/peerings/{peering_id}/accept
- Parameter description
Table 1 URI parameter description Parameter
Mandatory
Description
peering_id
Yes
ID of the VPC peering connection.
Request
None
Response
- Example response
{ "status": "ACTIVE", "name": "myVpcaa", "tenant_id": "2a62704287e74bdb90dc00ff4235748c", "request_vpc_info": { "vpc_id": "ecde182e-b7fa-4a8e-85f6-0db8bfa2583a", "tenant_id": "b17e103dab334f18b74335449d3eb763" }, "accept_vpc_info": { "vpc_id": "032d0cd5-4121-4b6c-9170-0dc4337173f6", "tenant_id": "2a62704287e74bdb90dc00ff4235748c" }, "id": "0a5a0dae-39f2-44a1-a6b7-bcc3383865a3" } - Parameter description
Table 2 Response parameters Parameter
Mandatory
Type
Description
status
Yes
String
Status of the request for accepting the VPC peering connection.
name
Yes
String
Name of the VPC peering connection.
tenant_id
Yes
String
Tenant ID.
vpc_id
Yes
String
ID of the VPC for which a route is to be added.
tenant_id
Yes
String
ID of the tenant who requests to add a route.
id
Yes
String
ID of a route.
Status Code
| Status Code | Description |
|---|---|
| 200 | The request of accepting the VPC peering connection succeeds. |
| 400 | The input parameter is invalid. |
| 500 | Failed to complete the request because of an internal service error. |
Error Code
For details, see Error Codes.
Last Article: Deleting a VPC Peering Connection
Next Article: Creating a Route to the Local VPC
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.