AWS elasticloadbalancing documentation change
Summary
Consolidated timeout error codes into TimedOut with expanded explanation including security group/TLS issues. Updated ConnectionReset and ResponseCodeMismatch descriptions.
Security assessment
Enhanced documentation explicitly links timeout errors to security configurations (security groups, TLS handshakes), improving troubleshooting guidance for security-related misconfigurations.
Diff
diff --git a/elasticloadbalancing/latest/application/load-balancer-health-check-logs.md b/elasticloadbalancing/latest/application/load-balancer-health-check-logs.md index 426a3b11e..7a00adceb 100644 --- a//elasticloadbalancing/latest/application/load-balancer-health-check-logs.md +++ b//elasticloadbalancing/latest/application/load-balancer-health-check-logs.md @@ -149,4 +149,3 @@ Code | Description -`RequestTimedOut` | Health check request timed out while waiting for response -`ConnectionTimedOut` | Health check failed because TCP connection attempt timed out -`ConnectionReset` | Health check failed due to connection reset -`ResponseCodeMismatch` | HTTP status code of the target’s response to the health check request did not match the configured status code +`TimedOut` | Health check failed because the connection attempt to the target timed out or the target did not respond within the configured health check timeout period. This can occur when the target's security group blocks inbound traffic on the health check port, the target is slow to respond, or the TLS handshake did not complete in time +`ConnectionReset` | Health check failed because the target reset or gracefully closed the connection before a valid response was returned +`ResponseCodeMismatch` | HTTP status code of the target's response to the health check request did not match the configured status code @@ -158,0 +158,4 @@ Code | Description +###### Note + +The new `TimedOut` error reason code replaces the `RequestTimedOut` and `ConnectionTimedOut` reason codes. +