resource/aws_guardduty_detector: Kubernetes events with GuardDuty

[parente]

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

GuardDuty now supports Elastic Kubernetes Service (EKS) audit log monitoring. Can the aws_guardduty_detector resource support a boolean switch to turn it on / off like it does for S3?

New or Affected Resource(s)

• aws_guardduty_detector

Potential Terraform Configuration

resource "aws_guardduty_detector" "my_detector" {
  enable = true

  datasources {
    s3_logs {
      enable = true
    }
    eks_logs {
      enable = true
    }
  }
}

References

• Announcement: https://aws.amazon.com/about-aws/whats-new/2022/01/amazon-guardduty-elastic-kubernetes-service-clusters/
• API documentation, for individual or organization setups: https://docs.aws.amazon.com/guardduty/latest/ug/kubernetes-protection.html
• How this was implemented for S3 events: resource/aws_guardduty_detector: S3 events with GuardDuty #14607

[mkmqsec]

I think this change would also affect the aws_guardduty_organization_configuration resource as well.

[robbie-daniels]

I think this change would also affect the aws_guardduty_organization_configuration resource as well.

Yeah, I think there would be a counterpart to the s3_logs datasource field

[mathewmoon]

Absolutely. I see this more as an important bug.

[woz5999]

any progress on this?

[danh-git]

Any update please?

[github-actions]

This functionality has been released in v4.17.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.