AWSAmazon GuardDutyaws_guardduty_detectorPro

How to Import an AWS GuardDuty Detector into Terraform

To import an existing AWS GuardDuty Detector into Terraform, scan it with Terraback and run terraback aws import --method bulk. Terraback writes the matching aws_guardduty_detector 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 detector ID (for example, 12abc34d567e8fa901bc2d34e56789f0).

Import AWS GuardDuty Detector with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Amazon GuardDuty resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS GuardDuty Detector 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_guardduty_detector.main
  id = "12abc34d567e8fa901bc2d34e56789f0"
}

Example aws_guardduty_detector configuration

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

resource "aws_guardduty_detector" "main" {
  enable                       = true
  finding_publishing_frequency = "SIX_HOURS"
}

Gotchas when importing a AWS GuardDuty Detector

  • There is one detector per account per region; importing the existing detector avoids the 'detector already exists' error on first apply.
  • The data source toggles (S3 logs, Kubernetes audit logs, malware protection) are increasingly managed via the separate aws_guardduty_detector_feature resource in newer provider versions.
  • Member account invitations, IP sets, threat intel sets, and filters are all separate GuardDuty resources.
  • Disabling the detector (enable = false) suspends findings rather than deleting history; destroying it removes the detector entirely.

Doing it manually with terraform import

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