How to Import an AWS Transit Gateway Peering Attachment Accepter into Terraform

Import AWS Transit Gateway Peering Attachment Accepter with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Amazon VPC Transit Gateway resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS Transit Gateway Peering Attachment Accepter to managed Terraform.

terraback scan all aws --region us-east-1

terraback aws import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = aws_ec2_transit_gateway_peering_attachment_accepter.example
  id = "tgw-attach-12345678"
}

Example aws_ec2_transit_gateway_peering_attachment_accepter configuration

Here is a realistic AWS Transit Gateway Peering Attachment Accepter block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_ec2_transit_gateway_peering_attachment_accepter" "example" {
  transit_gateway_attachment_id = "tgw-attach-12345678"

  tags = {
    Name = "example-peering-accepter"
  }
}

Gotchas when importing a AWS Transit Gateway Peering Attachment Accepter

• This resource manages the accepter side only; the requester side is aws_ec2_transit_gateway_peering_attachment, and both share the same tgw-attach ID but live in different accounts or regions.
• Import it in the peer account/region that owns the acceptance, not the requester's; using the wrong provider alias imports into the wrong side of the peering.
• transit_gateway_attachment_id is force-new and references the existing attachment; it must already be in state or visible to the accepter account before import.
• Importing does not change the peering's accepted state on its own; if the attachment is still pendingAcceptance, the apply will accept it, so review the plan before applying.

Doing it manually with terraform import

The native approach is to write the aws_ec2_transit_gateway_peering_attachment_accepter block by hand, then run terraform import aws_ec2_transit_gateway_peering_attachment_accepter.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other AWS resources