-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
aws-elasticloadbalancingv2: support tcp idle timeout for Network Load Balancer #31310
aws-elasticloadbalancingv2: support tcp idle timeout for Network Load Balancer #31310
Comments
Hi @mazyu36 , thanks for requesting this. As mentioned in the LoadBalancerAttribute and the CLI reference, the idle timeout is available for ALB only. To set the load balancer attributes thru CLI, I tried running the command like this. Please note that this is for HTTP Application load balancer which I referenced here.(have not run using CDK , trying that for now)
and you are correct in saying Cloudformation does not support TCP Idle timeout for NLB as clearly mentioned in the above referenced doc here -
For the support by cloudormation, you could create an issue with Cloudformation team by adding it on the Coverage roadmap |
@mazyu36 I tried deploying using Escape hatches, as a workaround to set the idle timeout from 60 to 600 seconds, it succeeded with ALB. Sharing the code snippet - const lb = new elbv2.ApplicationLoadBalancer(this, 'LB', {
vpc: new ec2.Vpc(this, 'VPC'),
internetFacing: true,
loadBalancerName:"lbname"
});
(lb.node.defaultChild as elbv2.CfnLoadBalancer).loadBalancerAttributes = [
{
key: 'idle_timeout.timeout_seconds',
value: '600'
}
]; But when i changed it to - key: 'tcp.idle_timeout.timeout_seconds', it failed with this error -
So this is reproducible. I highly doubt if |
Hi, @khushail. I'm sorry for causing confusion. Therefore, I think there is no need to support Since I think there is currently no way to set the Listener attribute, I have raised an issue as follows: |
sounds good. Thanks for the clarification @mazyu36 and raising the issue with Cloudformation team. :) |
@mazyu36 Cloudformation now supports |
@badmintoncryer |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
Describe the feature
AWS Network Load Balancer now supports configurable TCP idle timeout.
Announcement: https://aws.amazon.com/about-aws/whats-new/2024/09/aws-network-load-balancer-tcp-idle-timeout/
Use Case
To set idle timeout for NLB.
Proposed Solution
It is likely that it cannot be set at present, and we need to wait for CloudFormation support.
It is necessary to set
tcp.idle_timeout.seconds
in the listener's Attributes.https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-nlb-tcp-configurable-idle-timeout/
However, there is no way to configure it using CloudFormation.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-listener.html
I also tried adding it to the load balancer's attributes, like with ALB, but I couldn't do it.
Other Information
No response
Acknowledgements
CDK version used
all
Environment details (OS name and version, etc.)
all
The text was updated successfully, but these errors were encountered: