AWSAmazon VPCaws_vpc_endpointPro

How to Import an AWS VPC Endpoint into Terraform

To import an existing AWS VPC Endpoint into Terraform, scan it with Terraback and run terraback aws import --method bulk. Terraback writes the matching aws_vpc_endpoint resource block and the Terraform 1.5+ import block for you, so you do not have to run terraform import by hand. The import ID is the VPC endpoint ID (for example, vpce-0a1b2c3d4e5f6a7b8).

Import AWS VPC Endpoint with Terraback (recommended)

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

1

Scan your AWS account

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

Generate import blocks and import into state

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_vpc_endpoint.s3
  id = "vpce-0a1b2c3d4e5f6a7b8"
}

Example aws_vpc_endpoint configuration

Here is a realistic AWS VPC Endpoint block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_vpc_endpoint" "s3" {
  vpc_id            = "vpc-0a1b2c3d4e5f6a7b8"
  service_name      = "com.amazonaws.us-east-1.s3"
  vpc_endpoint_type = "Gateway"
  route_table_ids   = ["rtb-0a1b2c3d4e5f6a7b8"]
}

Gotchas when importing a AWS VPC Endpoint

  • Import by the vpce- ID.
  • Gateway endpoints use route_table_ids while Interface and GatewayLoadBalancer endpoints use subnet_ids and security_group_ids; copy only the fields valid for the endpoint type.
  • Route table and subnet associations can also be expressed as separate aws_vpc_endpoint_route_table_association / aws_vpc_endpoint_subnet_association resources; do not mix the two styles.
  • private_dns_enabled applies only to Interface endpoints; setting it on a Gateway endpoint is invalid.

Doing it manually with terraform import

The native approach is to write the aws_vpc_endpoint block by hand, then run terraform import aws_vpc_endpoint.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 your whole AWS account in minutes

Terraback scans 80+ AWS resource types and emits clean Terraform plus import blocks, running locally with read-only credentials. $499 once, no SaaS.