» Resource: aws_vpc_peering_connection_accepter

Provides a resource to manage the accepter's side of a VPC Peering Connection.

When a cross-account (requester's AWS account differs from the accepter's AWS account) or an inter-region VPC Peering Connection is created, a VPC Peering Connection resource is automatically created in the accepter's account. The requester can use the aws_vpc_peering_connection resource to manage its side of the connection and the accepter can use the aws_vpc_peering_connection_accepter resource to "adopt" its side of the connection into management.

» Example Usage

provider "aws" {
  region = "us-east-1"

  # Requester's credentials.

provider "aws" {
  alias  = "peer"
  region = "us-west-2"

  # Accepter's credentials.

resource "aws_vpc" "main" {
  cidr_block = ""

resource "aws_vpc" "peer" {
  provider   = "aws.peer"
  cidr_block = ""

data "aws_caller_identity" "peer" {
  provider = "aws.peer"

# Requester's side of the connection.
resource "aws_vpc_peering_connection" "peer" {
  vpc_id        = "${aws_vpc.main.id}"
  peer_vpc_id   = "${aws_vpc.peer.id}"
  peer_owner_id = "${data.aws_caller_identity.peer.account_id}"
  peer_region   = "us-west-2"
  auto_accept   = false

  tags = {
    Side = "Requester"

# Accepter's side of the connection.
resource "aws_vpc_peering_connection_accepter" "peer" {
  provider                  = "aws.peer"
  vpc_peering_connection_id = "${aws_vpc_peering_connection.peer.id}"
  auto_accept               = true

  tags = {
    Side = "Accepter"

» Argument Reference

The following arguments are supported:

  • vpc_peering_connection_id - (Required) The VPC Peering Connection ID to manage.
  • auto_accept - (Optional) Whether or not to accept the peering request. Defaults to false.
  • tags - (Optional) A map of tags to assign to the resource.

» Removing aws_vpc_peering_connection_accepter from your configuration

AWS allows a cross-account VPC Peering Connection to be deleted from either the requester's or accepter's side. However, Terraform only allows the VPC Peering Connection to be deleted from the requester's side by removing the corresponding aws_vpc_peering_connection resource from your configuration. Removing a aws_vpc_peering_connection_accepter resource from your configuration will remove it from your statefile and management, but will not destroy the VPC Peering Connection.

» Attributes Reference

All of the argument attributes except auto_accept are also exported as result attributes.

» Accepter and Requester Attributes Reference

  • allow_remote_vpc_dns_resolution - Indicates whether a local VPC can resolve public DNS hostnames to private IP addresses when queried from instances in a peer VPC.
  • allow_classic_link_to_remote_vpc - Indicates whether a local ClassicLink connection can communicate with the peer VPC over the VPC Peering Connection.
  • allow_vpc_to_remote_classic_link - Indicates whether a local VPC can communicate with a ClassicLink connection in the peer VPC over the VPC Peering Connection.

» Attributes Reference

In addition to all arguments above, the following attributes are exported:

  • id - The ID of the VPC Peering Connection.

» Import

VPC Peering Connection Accepters can be imported by using the Peering Connection ID, e.g.

$ terraform import aws_vpc_peering_connection_accepter.example pcx-12345678

Certain resource arguments, like auto_accept, do not have an EC2 API method for reading the information after peering connection creation. If the argument is set in the Terraform configuration on an imported resource, Terraform will always show a difference. To workaround this behavior, either omit the argument from the Terraform configuration or use ignore_changes to hide the difference, e.g.

resource "aws_vpc_peering_connection_accepter" "example" {
  # ... other configuration ...

  # There is no AWS EC2 API for reading auto_accept
  lifecycle {
    ignore_changes = ["auto_accept"]