-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Support for JsonBody in fields to match on WAF ByteMatch rule #18515
Comments
It's been over a year since this feature came out, and nearly as long since this was reported. One of our rules requires Given that there is no activity on this, I'm hoping someone has had some luck with a workaround. Any ideas short of using a null_resource with the CLI to do this properly? :( |
Blocked on this as well. I'll put together a PR, if no one else has made a start. |
I see that this PR is stale for a long time. Which is a shame because of the work that is done by @steveorourke. |
Code has been reviewed and tested. LGMT! 👍🏼 |
Thanks @tiborhercz. I've accepted all suggestions. |
Thanks @steveorourke @bschaatsbergen Could you please also take a look? |
This functionality has been released in v4.29.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
Was trying to implement some WAF rules and noticed that the Console lets you make ones which target the parsed JsonBody instead of the raw Body.
This feature was released Feb 2021 and would be very helpful in blocking invalid requests.
New or Affected Resource(s)
Potential Terraform Configuration
Just the statement portion for hypothetically ensuring a graphql query has "viewer" somewhere in the query field.
References
The text was updated successfully, but these errors were encountered: