Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

AcceptVpcPeeringConnection - Amazon Elastic Compute Cloud

AcceptVpcPeeringConnection

Accept a VPC peering connection request. To accept a request, the VPC peering connection must be in the pending-acceptance state, and you must be the owner of the peer VPC. Use DescribeVpcPeeringConnections to view your outstanding VPC peering connection requests.

For an inter-Region VPC peering connection request, you must accept the VPC peering connection in the Region of the accepter VPC.

Request Parameters

The following parameters are for this specific action. For more information about required and optional parameters that are common to all actions, see Common Query Parameters.

DryRun

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

Type: Boolean

Required: No

VpcPeeringConnectionId

The ID of the VPC peering connection. You must specify this parameter in the request.

Type: String

Required: Yes

Response Elements

The following elements are returned by the service.

requestId

The ID of the request.

Type: String

vpcPeeringConnection

Information about the VPC peering connection.

Type: VpcPeeringConnection object

Errors

For information about the errors that are common to all actions, see Common client error codes.

Examples

Example

This example accepts the specified VPC peering connection request.

Sample Request

https://ec2.amazonaws.com/?Action=AcceptVpcPeeringConnection &VpcPeeringConnectionId=pcx-1a2b3c4d &AUTHPARAMS

Sample Response

<AcceptVpcPeeringConnectionResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/"> <requestId>7a62c49f-347e-4fc4-9331-6e8eEXAMPLE</requestId> <vpcPeeringConnection> <vpcPeeringConnectionId>pcx-1a2b3c4d</vpcPeeringConnectionId> <requesterVpcInfo> <ownerId>123456789012</ownerId> <vpcId>vpc-1a2b3c4d</vpcId> <cidrBlock>10.0.0.0/28</cidrBlock> </requesterVpcInfo> <accepterVpcInfo> <ownerId>777788889999</ownerId> <vpcId>vpc-111aaa22</vpcId> <cidrBlock>10.0.1.0/28</cidrBlock> <peeringOptions> <allowEgressFromLocalClassicLinkToRemoteVpc>false</allowEgressFromLocalClassicLinkToRemoteVpc> <allowEgressFromLocalVpcToRemoteClassicLink>false</allowEgressFromLocalVpcToRemoteClassicLink> <allowDnsResolutionFromRemoteVpc>false</allowDnsResolutionFromRemoteVpc> </peeringOptions> </accepterVpcInfo> <status> <code>active</code> <message>Active</message> </status> <tagSet/> </vpcPeeringConnection> </AcceptVpcPeeringConnectionResponse>"

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following:

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.