README.md

This module enables AWS GuardDuty in one region of one account with comprehensive threat detection features and optionally sets up an SNS topic to receive notifications of its findings.

The module supports enabling various GuardDuty detector features including:

• S3 Data Events Protection - Monitors S3 data plane operations for suspicious activity
• EKS Audit Logs - Analyzes Kubernetes audit logs for threat detection in EKS clusters
• EBS Malware Protection - Scans EC2 instance EBS volumes for malware
• Lambda Network Logs - Monitors Lambda function network activity for threats
• Runtime Monitoring - Provides threat detection for EC2, ECS, and EKS runtime environments with agent management
• EKS Runtime Monitoring - Standalone EKS runtime threat detection (alternative to full Runtime Monitoring)

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Introduction

Features

This module provides comprehensive AWS GuardDuty configuration with support for all major detector features:

Threat Detection Features

• S3 Data Events Protection (s3_protection_enabled)

  • Monitors S3 bucket data plane operations (GetObject, PutObject, DeleteObject, etc.)
  • Detects suspicious access patterns and potential data exfiltration attempts

• EKS Audit Logs (kubernetes_audit_logs_enabled)

  • Analyzes Kubernetes API server audit logs for EKS clusters
  • Identifies suspicious kubectl commands, unauthorized access, and privilege escalation attempts

• EBS Malware Protection (malware_protection_scan_ec2_ebs_volumes_enabled)

  • Scans EBS volumes attached to EC2 instances for malware
  • Agentless malware detection using snapshots

• Lambda Network Logs (lambda_network_logs_enabled)

  • Monitors Lambda function network connections
  • Detects connections to known malicious IPs or unexpected network behavior

• Runtime Monitoring (runtime_monitoring_enabled)

  • Provides comprehensive runtime threat detection for EC2, ECS, and EKS resources
  • Monitors runtime activity including file access, process execution, and network connections
  • Supports automatic agent management for EKS add-ons, ECS Fargate, and EC2 instances
  • Note: Runtime Monitoring already includes EKS protection; do not enable both runtime_monitoring_enabled and eks_runtime_monitoring_enabled

• EKS Runtime Monitoring (eks_runtime_monitoring_enabled)

  • Standalone EKS-only runtime monitoring (use when you only need EKS protection)
  • Lighter alternative to full Runtime Monitoring
  • Automatically manages EKS security agent add-ons

SNS and CloudWatch Integration

• Optional SNS topic creation for findings notifications
• CloudWatch Events integration for real-time alerting
• Configurable finding publishing frequency (FIFTEEN_MINUTES, ONE_HOUR, SIX_HOURS)
• Support for multiple SNS subscribers (SQS, Lambda, HTTPS endpoints, etc.)

Important Notes

• RDS Login Events can only be configured at the organization level via aws_guardduty_organization_configuration_feature, not at the detector level
• Runtime Monitoring vs EKS Runtime Monitoring: These are mutually exclusive. Runtime Monitoring provides broader coverage (EC2, ECS, EKS), while EKS Runtime Monitoring is EKS-specific
• All detector features use the newer aws_guardduty_detector_feature resource instead of the deprecated datasources block

Usage

Here's how to invoke this module in your projects

Basic Example

module "guardduty" {
  source = "cloudposse/guardduty/aws"
  # version = "x.x.x"

  create_sns_topic = true
  subscribers = {
    opsgenie = {
      protocol               = "https"
      endpoint               = "https://api.example.com/v1/"
      endpoint_auto_confirms = true
      raw_message_delivery   = false
    }
  }

  context = module.this.context
}

Complete Example with All Features Enabled

module "guardduty" {
  source = "cloudposse/guardduty/aws"
  # version = "x.x.x"

  # SNS and CloudWatch configuration
  create_sns_topic                          = true
  enable_cloudwatch                         = true
  cloudwatch_event_rule_pattern_detail_type = "GuardDuty Finding"
  finding_publishing_frequency              = "FIFTEEN_MINUTES"

  subscribers = {
    opsgenie = {
      protocol               = "https"
      endpoint               = "https://api.example.com/v1/"
      endpoint_auto_confirms = true
      raw_message_delivery   = false
    }
  }

  # GuardDuty detector features
  s3_protection_enabled                           = true
  kubernetes_audit_logs_enabled                   = true
  malware_protection_scan_ec2_ebs_volumes_enabled = true
  lambda_network_logs_enabled                     = true

  # Runtime Monitoring with all agent management features
  runtime_monitoring_enabled = true
  runtime_monitoring_additional_config = {
    eks_addon_management_enabled         = true
    ecs_fargate_agent_management_enabled = true
    ec2_agent_management_enabled         = true
  }

  # Note: Do not enable both runtime_monitoring_enabled and eks_runtime_monitoring_enabled
  # Runtime Monitoring already includes EKS protection
  eks_runtime_monitoring_enabled = false

  context = module.this.context
}

Example with EKS Runtime Monitoring Only

module "guardduty" {
  source = "cloudposse/guardduty/aws"
  # version = "x.x.x"

  # If you only need EKS runtime monitoring (not EC2/ECS)
  eks_runtime_monitoring_enabled = true
  runtime_monitoring_additional_config = {
    eks_addon_management_enabled = true
  }

  # Do not enable runtime_monitoring_enabled when using eks_runtime_monitoring_enabled
  runtime_monitoring_enabled = false

  context = module.this.context
}

Examples

Here is an example of using this module:

• examples/complete - complete example of using this module

Requirements

Providers

Modules

Resources

Inputs

{
  "additional_tag_map": {},
  "attributes": [],
  "delimiter": null,
  "descriptor_formats": {},
  "enabled": true,
  "environment": null,
  "id_length_limit": null,
  "label_key_case": null,
  "label_order": [],
  "label_value_case": null,
  "labels_as_tags": [
    "unset"
  ],
  "name": null,
  "namespace": null,
  "regex_replace_chars": null,
  "stage": null,
  "tags": {},
  "tenant": null
}

[
  "default"
]

object({
    eks_addon_management_enabled         = optional(bool, false)
    ecs_fargate_agent_management_enabled = optional(bool, false)
    ec2_agent_management_enabled         = optional(bool, false)
  })

map(object({
    protocol               = string
    endpoint               = string
    endpoint_auto_confirms = bool
    raw_message_delivery   = bool
  }))

Outputs

Related Projects

Check out these related projects.

• terraform-null-label - Terraform module designed to generate consistent names and tags for resources. Use terraform-null-label to implement a strict naming convention.
• terraform-aws-security-hub - Terraform module to deploy AWS Security Hub
• terraform-aws-config - Terraform module to enable AWS Config and optionally sets up an SNS topic to receive notifications of its findings.

References

For additional context, refer to some of these links.

• AWS GuardDuty Documentation - Official AWS GuardDuty documentation
• AWS GuardDuty Detector Features - GuardDuty features activation model and available detector features
• Terraform aws_guardduty_detector Resource - Terraform resource for managing GuardDuty detectors
• Terraform aws_guardduty_detector_feature Resource - Terraform resource for configuring GuardDuty detector features
• GuardDuty Finding Types - Complete list of GuardDuty finding types
• GuardDuty Runtime Monitoring - Runtime Monitoring for threat detection in EC2, ECS, and EKS resources

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

1. Review our Code of Conduct and Contributor Guidelines.
2. Fork the repo on GitHub
3. Clone the project to your own machine
4. Commit changes to your own branch
5. Push your work back up to your fork
6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Running Terraform Tests

We use Atmos to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.

All tests are located in the test/ folder.

Under the hood, tests are powered by Terratest together with our internal Test Helpers library, providing robust infrastructure validation.

Setup dependencies:

• Install Atmos (installation guide)
• Install Go 1.24+ or newer
• Install Terraform or OpenTofu

To run tests:

• Run all tests:

  atmos test run
  

• Clean up test artifacts:

  atmos test clean
  

• Explore additional test options:

  atmos test --help
  

The configuration for test commands is centrally managed. To review what's being imported, see the atmos.yaml file.

Learn more about our automated testing in our documentation or implementing custom commands with atmos.

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

Copyrights

Copyright © 2020-2026 Cloud Posse, LLC