-
Notifications
You must be signed in to change notification settings - Fork 4k
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
📊Tracking: AWS WAFV2 #6878
Comments
Really looking forward to this! :) The WAFv2 CFN spec is very complex and error-prone for somebody new to it, especially compared to the clean web UI. |
@SomayaB, working on an L2 construct for this as part of another project. Happy to contribute back to the main branch if no-one else is working this. |
It looks like yamatatsu is beating me to it (I am half a year late sooooooo....lol): |
This issue has received a significant amount of attention so we are automatically upgrading its priority. A member of the community will see the re-prioritization and provide an update on the issue. |
Add your +1 👍 to help us prioritize high-level constructs for this service
Overview:
This is the latest version of the AWS WAF API, AWS WAF is a web application firewall that lets you monitor the HTTP and HTTPS requests that are forwarded to Amazon CloudFront, an Amazon API Gateway API, or an Application Load Balancer. AWS WAF also lets you control access to your content. Based on conditions that you specify, such as the IP addresses that requests originate from or the values of query strings, API Gateway, CloudFront, or the Application Load Balancer responds to requests either with the requested content or with an HTTP 403 status code (Forbidden). You also can configure CloudFront to return a custom error page when a request is blocked.
AWS Docs
Maturity: CloudFormation Resources Only
See the AWS Construct Library Module Lifecycle doc for more information about maturity levels.
Implementation:
See the CDK API Reference for more implementation details.
Issue list:
This is a 📊Tracking Issue
The text was updated successfully, but these errors were encountered: