-
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
AWS SecurityHub: the ability to disable specific compliance controls #11624
Comments
Looks like that was merged. What's next? |
Any updates on this? |
@ewaltman or @brettcave anything I can do to help push this over the line? |
@phundisk - I haven't looked at this in a while, I will revisit this. |
@brettcave (or @ewbankkit) Gentle nudge to see if you've had a chance to take a look at the PR for this issue. If there's any other way for us to get hashicorp to review stale issues/PRs like this, that would be helpful to know. In the past, thumbs up on the issue was possibly used to triage work, but that seems unreliable and in some cases doesn't seem to make an impact to priority. |
@ewbankkit @DrFaust92 @bflad Can someone please let us know what is needed to get someone to look at this PR/issue? |
We've added support for this to our |
This functionality has been released in v3.50.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. |
Community Note
Description
As of Jan 15, 2020, AWS now allows to disable specific compliance controls within AWS SecurityHub. It will be very useful in my case to disable some of them or the ones that are not relevant for my setup.
New or Affected Resource(s)
Potentially new resource
References
The text was updated successfully, but these errors were encountered: