-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement]: aws_guardduty_detector Lambda Protection support #30859
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
GuardDuty API changes in March 2023#Mapping dataSources to features According to the official documentation above, it appears that the However, this provider does not currently support the See #30303 . |
You will be able to use the upcoming resource "aws_guardduty_detector" "example" {
enable = true
}
resource "aws_guardduty_detector_feature" "example" {
detector_id = aws_guardduty_detector.example.id
name = "LAMBDA_NETWORK_LOGS"
status = "ENABLED"
} |
This functionality has been released in v5.20.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! |
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. |
Description
Amazon GuardDuty now supports Lambda Protection but the terraform resource for GuardDuty does not yet support it.
It would be great if we could enable GuardDuty Lambda Protection with terraform resource
aws_guardduty_detector
.Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: