[Enhancement]: Add support for auto-enabling lambda scanning on aws_inspector2_organization_configuration

[srgustafson8]

Description

At the end of November, AWS introduced Lambda scanning for Inspector v2. You can currently enable scanning of Lambdas using aws_inspector2_enabler for individual accounts, but are currently unable to set it for the whole organization using the aws_inspector2_organization_configuration block. This issue is to add the capability to enable Lambda scanning organization wide.

Affected Resource(s) and/or Data Source(s)

aws_inspector2_organization_configuration

Potential Terraform Configuration

resource "aws_inspector2_organization_configuration" "example" {
  auto_enable {
    ec2    = true
    ecr    = false
    lambda = true
  }
}

References

https://docs.aws.amazon.com/inspector/latest/user/enable-disable-scanning-lambda.html

https://docs.aws.amazon.com/inspector/v2/APIReference/API_UpdateOrganizationConfiguration.html

Would you like to implement a fix?

Yes

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

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