Skip to content

Conversation

yamoyamoto
Copy link
Contributor

The documentation stated that ELB couldn't change the healthy response code. However, since both NLB and ALB now support 4xx codes, I've removed this example from the description.

ALB

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/target-group-health-checks.html
Matcher: If the protocol version is HTTP/1.1 or HTTP/2, the possible values are from 200 to 499.

NLB

https://docs.aws.amazon.com/elasticloadbalancing/latest/network/target-group-health-checks.html
Matcher: [HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target. The range is 200 to 599. The default is 200-399.

NLB support for this feature was added in November 2022

https://aws.amazon.com/about-aws/whats-new/2022/11/elastic-load-balancing-capabilities-application-availability/
Network Load Balancer (NLB) Health Check Improvements: NLB allows customers to define health check intervals, specify HTTP response codes that determine target health, and configure the number of consecutive health check responses before a target is either health or unhealthy. For details, see the NLB health check documentation here.

@yamoyamoto yamoyamoto force-pushed the docs/update-elb-desc branch 2 times, most recently from 2568ae7 to f645e67 Compare October 2, 2024 23:58
…d Load Balancer

Signed-off-by: tomoya-kawaguchi <yamo7yamoto@gmail.com>
@yamoyamoto yamoyamoto force-pushed the docs/update-elb-desc branch from f645e67 to fdb5abb Compare October 3, 2024 00:00
@joaodrp joaodrp merged commit 0bfa293 into distribution:main Oct 3, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants