desync_mitigation_mode is not available in all AWS partitions.

[slimm609]

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.2.4

aws = {
source = "hashicorp/aws",
version = "4.22.0"
}

Affected Resource(s)

terraform-provider-aws/internal/service/elb/load_balancer.go

Line 257 in 77cbe28

"desync_mitigation_mode": {

I can't copy the full error but desync_mitigation_mode mode is not available in certain AWS partitions. With the default being set to on, this fails with an error of

Invalid AdditionalAttributes passed with key routing.http.desync_mitigation_mode

Panic Output

Expected Behavior

Not fail in other AWS partitions.

Actual Behavior

fails with error

Invalid AdditionalAttributes passed with key routing.http.desync_mitigation_mode

Important Factoids

This works fine in the commercial and gov partition but fails in other restricted partitions.

[rwd5213]

Should probably add label:partition/aws-iso and label:partition/aws-iso-b to this.

[Houlistonm]

@justinretzolk The few of us that run in non-public regions/partitions are never going to get the "up votes" due to our smaller community. How can we move these stories up the priority list?

[justinretzolk]

Hey @Houlistonm 👋 Thank you for checking in on this. I've added a couple of labels indicating that this affects the AWS-ISO and AWS-ISO-b to try to get it a bit of extra traction, given the more limited user base and thus less change of upvotes, as you called out.

[mroberts14]

Wondering if the only work around to this is to revert back to aws provider version 3.66.0 as the desync_mitigation_mode option was implemented in 3.67.0 as noted here: #14696 (comment) ?

I haven't tested it yet, but plan on trying it soon.

[mroberts14]

Wondering if the only work around to this is to revert back to aws provider version 3.66.0 as the desync_mitigation_mode option was implemented in 3.67.0 as noted here: #14696 (comment) ?

I haven't tested it yet, but plan on trying it soon.

Reverting back to 3.66.0 fixed the desync_mitigation_mode error for it not being available in iso-b, but then I ran into the ELB listener tags not being supported which is fixed in version v3.72.0 here #22551 so at the moment stuck on deploying ALB and CLB in iso-b until desync_mitigation_mode is configured as not required to deploy an CLB/ALB which might be similar to the implementation of this fix for S3 Object Lock #24809 where d.Set("object_lock_enabled", nil) instead of a required input.

[Houlistonm]

Any status on this issue?