AWS elasticloadbalancing documentation change
Summary
Restructured documentation with clearer instructions, added CLI examples, and explicit timeout constraints
Security assessment
Improves operational documentation for TCP idle timeout configuration but doesn't address security vulnerabilities or introduce new security features
Diff
diff --git a/elasticloadbalancing/latest/network/update-idle-timeout.md b/elasticloadbalancing/latest/network/update-idle-timeout.md index 26518f337..ecb25a742 100644 --- a//elasticloadbalancing/latest/network/update-idle-timeout.md +++ b//elasticloadbalancing/latest/network/update-idle-timeout.md @@ -7 +7 @@ -For each TCP request made through a Network Load Balancer, the state of that connection is tracked. If no data is sent through the connection by either the client or target for longer than the idle timeout, the connection is closed. The default idle timeout value for TCP flows is 350 seconds, but can be updated to any value between 60-6000 seconds. +For each TCP request made through a Network Load Balancer, the state of that connection is tracked. If no data is sent through the connection by either the client or target for longer than the idle timeout, the connection is closed. @@ -9 +9 @@ For each TCP request made through a Network Load Balancer, the state of that con -The connection idle timeout for TLS listeners is 350 seconds and can't be modified. +###### Considerations @@ -11 +11,11 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi -###### To update the TCP idle timeout using the console + * The default idle timeout value for TCP flows is 350 seconds. + + * The connection idle timeout for TLS listeners is 350 seconds and can't be modified. + + + + +Console + + +###### To update the TCP idle timeout @@ -17 +27 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi - 3. Select the Network Load Balancer. + 3. Select the check box for the Network Load Balancer. @@ -19 +29 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi - 4. On the listeners tab choose the **Actions** , **View listener details**. + 4. On the listeners tab, select the check box for the TCP listener and then choose **Actions** , **View listener details**. @@ -21 +31 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi - 5. On the listener details page, in the **Attributes** tab, select **Edit**. + 5. On the listener details page, in the **Attributes** tab, select **Edit**. If the listener uses a protocol other than TCP, this tab is not present. @@ -23 +33 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi - 6. On the **Edit listener attributes** page, in the **Listener attributes** section, enter a value for **TCP idle timeout**. + 6. Enter a value for **TCP idle timeout** from 60-6000 seconds. @@ -25 +35 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi - 7. Choose **Save changes** + 7. Choose **Save changes**. @@ -30 +40,4 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi -###### To update the TCP idle timeout using the AWS CLI +AWS CLI + + +###### To update the TCP idle timeout @@ -33,0 +47,17 @@ Use the [modify-listener-attributes](https://docs.aws.amazon.com/cli/latest/refe + + aws elbv2 modify-listener-attributes \ + --listener-arn arn:aws:elasticloadbalancing:us-east-2:123456789012:listener/net/my-load-balancer/1234567890123456/1234567890123456 \ + --attributes Key=tcp.idle_timeout.seconds,Value=500 + +The following is example output. + + + { + "Attributes": [ + { + "Key": "tcp.idle_timeout.seconds", + "Value": "500" + } + ] + } +