You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Rafaellinos! Sorry for this confusing situation.
The error message you've described seems to originate from the AWS load balancer API, and not from Terraform itself.
I'm not familiar enough with the load balancer API to know whether this is a bug in Terraform's AWS provider or if this is describing a genuine problem with your configuration, but I do note from the ELBv2 documentation that there is indeed a property named client_keep_alive.seconds and that 3600 ought to be a valid value for it when you are configuring an Application Load Balancer, so this does seem like possibly an AWS provider bug.
Because of that, I recommend that you report this bug in the AWS provider's GitHub repository. The AWS provider maintainers are far more familiar with AWS service behavior and so can hopefully confirm whether this is an AWS provider bug or if there is a different way you could write this configuration to get a successful result.
Since there doesn't seem to be anything we could change in Terraform Core to improve this situation -- the behaviors involved belong to the AWS provider and to the AWS ELBv2 API -- I'm going to close this issue. Thanks!
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/Rafaellinos/49618fec23afd1454cc6212d7b6c4258
Expected Behavior
Create ALB in localstack.
Actual Behavior
I tried to remove and add the client_keep_alive configuration, but no success.
Steps to Reproduce
tflocal init
tflocal apply
Additional Context
Using:
aws-cli = 2.15.40
localstack pro (trial) = 3.4.0
024-04-26T17:39:45.002 INFO --- [ asgi_gw_5] localstack.request.aws : AWS elbv2.DescribeLoadBalancers => 200
2024-04-26T17:39:45.007 INFO --- [ asgi_gw_4] localstack.request.aws : AWS elbv2.ModifyLoadBalancerAttributes => 400 (InvalidConfigurationRequest)
References
No response
The text was updated successfully, but these errors were encountered: