feat: configurable NLB → ALB health check protocol and path - #33
Merged
Conversation
… target groups Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
gauravjain99
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The NLB target group defaults to HTTP on
/, which fails when the backing ALB is configured for HTTPS-only traffic. Consumers need a way to override the health check protocol, path, and port to match their ALB's requirements.How?
A new optional
NlbHealthCheckConfiginterface is added toNetworkLoadBalancerConfig, and the health check is applied to the NLB target group for both new and existing ALB configurations. README documentation and a config reference table are added for discoverability.