forwarded_ip_config support for geo_match_statement

[cisnerosk]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS Supported X-Forwarded-For in AWS WAFv2. I am able to set this up via the AWS console. In my situation am experimenting with a way to have an or statement that says

if a request matches at least of the or statements:

1. originates from a country in: COUNTRY by source IP address
   OR
2. originates from a country in: COUNTRY by IP address in header, header filed name X-Forwarded-For and the fallback action for missing IP address to be "no-match"

Please let me know if this is sufficient information. Running aws provider version 2.68, terraform version 12.27.

New or Affected Resource(s)

• aws_wafv2_web_acl

Potential Terraform Configuration

resource "aws_wafv2_web_acl" "example" {
  name        = "or-statement-geo-match-example"
  description = "Example of an or statement with geo match statement."
  scope       = "REGIONAL"

  default_action {
    block {}
  }

  rule {
        name = "rule1"
        priority = 1

        action {
            block {}
        }

        statement {
            or_statement {
                statement {
                    geo_match_statement {
                        country_codes = ["COUNTRY"]
                    }
                },
                statement {
                    geo_match_statement {
                        country_codes = ["COUNTRY"]
                    }
                      forwarded_ip_config {
                          header_name = "X-Forwarded-For"
                          fallback_behavior = "NO-MATCH"
                      }
                }
        }
        visibility_config {
            cloudwatch_metrics_enabled = true
            metric_name = "or-statement-geo-match-example"
            sampled_requests_enabled = true 
        }
    }
}

References

https://aws.amazon.com/about-aws/whats-new/2020/07/support-x-forwarded-for-header-available-aws-waf/

• Support for X-Forwarded-For header in aws_wafv2_web_acl rate_based_statement #14480

[anGie44]

This feature has been merged and will release with v3.3.0 of the Terraform AWS Provider, likely out later this evening (EST).

[ghost]

This has been released in version 3.3.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!