AWSAmazon VPCaws_security_groupPro

How to Import an AWS Security Group into Terraform

To import an existing AWS Security Group into Terraform, scan it with Terraback and run terraback aws import --method bulk. Terraback writes the matching aws_security_group 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 security group ID (for example, sg-0123456789abcdef0).

Import AWS Security Group 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 Security Group 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_security_group.web
  id = "sg-0123456789abcdef0"
}

Example aws_security_group configuration

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

resource "aws_security_group" "web" {
  name        = "web-sg"
  description = "Allow HTTP and HTTPS"
  vpc_id      = "vpc-0a1b2c3d4e5f6a7b8"

  ingress {
    from_port   = 443
    to_port     = 443
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }

  egress {
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["0.0.0.0/0"]
  }
}

Gotchas when importing a AWS Security Group

  • Import the group by its sg- ID, not its name.
  • If you manage rules as separate aws_vpc_security_group_ingress_rule / aws_security_group_rule resources, do not also declare inline ingress/egress blocks or Terraform will fight itself.
  • The description field is immutable; a mismatch forces replacement, so copy it exactly from the console.
  • The default security group of a VPC should use aws_default_security_group.

Doing it manually with terraform import

The native approach is to write the aws_security_group block by hand, then run terraform import aws_security_group.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.