aws guardduty organization configuration auto enable malware protection

[nickolivera]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

https://docs.aws.amazon.com/guardduty/latest/ug/malware-protection.html

NOTE: This deals only with the organization configuration

Requires update to 1.44.63

New or Affected Resource(s)

• aws_guardduty_organization_configuration

Potential Terraform Configuration

resource "aws_guardduty_organization_configuration" "example" {
  auto_enable = true
  detector_id = aws_guardduty_detector.example.id

  datasources {
    malware_protection {
      scan_ec2_instance_with_findings {
        ebs_volumes {
          auto_enable = true
        }
      }
    }
  }
}

References

Announcement.
Blog post.

• resource/aws_guardduty_organization_configuration: Add support for EKS Protection #25131
• aws guardduty organization configuration auto enable eks audit logs #25131 #25851

[github-actions]

This functionality has been released in v4.24.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.