Skip to content

Auto-generated

This page is generated by terraform-docs at build time from the infra/ repo. Do not edit manually.

GuardDuty

One GuardDuty detector per region with its protection features spelled out, plus the suppression filters for the three known-noise patterns from IS-111. Part of the account security baseline (IS-67).

Features are declared one resource each so the plan states what is on and off in every region. The GuardDuty API has no per-feature identity, so the feature resources cannot be imported: on first apply Terraform issues an UpdateDetector call that sets the status already in place.

Every filter archives, never deletes, and each one is scoped to the exact instances, principals or buckets it is for. The same finding type on any other resource stays visible; that is the escalation signal.

Requirements

Name Version
terraform >= 1.6.0
aws ~> 6.0

Providers

Name Version
aws 6.66.0

Modules

No modules.

Resources

Name Type
aws_guardduty_detector.this resource
aws_guardduty_detector_feature.runtime_monitoring resource
aws_guardduty_detector_feature.this resource
aws_guardduty_filter.crawler_dns resource
aws_guardduty_filter.known_operator_anomalies resource
aws_guardduty_filter.public_by_design_buckets resource

Inputs

Name Description Type Default Required
base_tags Base tags to apply to all resources map(string) {} no
crawler_instance_names Name tag values of instances whose DNS findings are archived (pattern 1). Empty disables the filter. list(string) [] no
features Protection features other than RUNTIME_MONITORING, keyed by feature name with ENABLED or DISABLED. The default is the estate's baseline: S3, EBS malware, RDS login and Lambda network protection on; EKS and the AI features off. map(string)
{
"AI_ANALYST": "DISABLED",
"AI_PROTECTION": "DISABLED",
"EBS_MALWARE_PROTECTION": "ENABLED",
"EKS_AUDIT_LOGS": "DISABLED",
"LAMBDA_NETWORK_LOGS": "ENABLED",
"RDS_LOGIN_EVENTS": "ENABLED",
"S3_DATA_EVENTS": "ENABLED"
}
no
finding_publishing_frequency How often GuardDuty re-publishes recurring findings: FIFTEEN_MINUTES, ONE_HOUR or SIX_HOURS string "SIX_HOURS" no
first_rank Rank of the first module filter; later filters count up from it. Raise it where the detector already has hand-made filters at lower ranks. number 1 no
known_operator_principals IAM user or role names whose IAMUser/AnomalousBehavior findings are archived (pattern 2). Empty disables the filter. list(string) [] no
name_prefix Prefix for the detector Name tag string n/a yes
public_by_design_buckets S3 buckets whose public-access findings are archived (pattern 3). Empty disables the filter. list(string) [] no
runtime_monitoring Enable Runtime Monitoring with the managed EC2 agent. On where the region runs compute, off elsewhere. bool false no

Outputs

Name Description
detector_arn ARN of the GuardDuty detector
detector_id ID of the GuardDuty detector