elbv2/lb: Validation error: Load balancer attribute key not recognized

[YakDriver]

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

Terraform CLI and Terraform AWS Provider Version

Terraform v1.1.7

• provider registry.terraform.io/hashicorp/aws v4.8.0

Affected Resource(s)

• aws_lb

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_lb" "lb_test" {
  name            = "autograf"
  internal        = true
  security_groups = [aws_security_group.alb_test.id]
  subnets         = aws_subnet.alb_test.*.id

  idle_timeout               = 30
  enable_deletion_protection = false

  tags = {
    Name = "Vandelux"
  }
}

Debug Output

failure configuring LB attributes: Validation error: Load balancer attribute key 'routing.http.desync_mitigation_mode' is not recognized

Expected Behavior

Load balancer creates and updates correctly.

Actual Behavior

Error above.

Steps to Reproduce

1. terraform apply

Important Factoids

Running in ISO environment.

References

• Support aws-iso, aws-iso-b, aws-iso-e, aws-iso-f partitions #18593
• aws_elb & aws_lb: Add desync_mitigation_mode #14764

[github-actions]

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