aws-elasticloadbalancingv2: health and unhealthy threshold counts can vary

[toxygene]

The validateTargetGroup method in the NetworkTargetGroup class has a check to ensure the healthy and unhealthy threshold counts are the same (https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-elasticloadbalancingv2/lib/nlb/network-target-group.ts#L262-L268), but this does not appear to be a requirement of AWS.

➜  aws elbv2 describe-target-groups --target-group-arns [omitted] --query 'TargetGroups[0].[HealthyThresholdCount,UnhealthyThresholdCount]'
[
    5,
    5
]

Expected Behavior

The NetworkTargetGroup is created

Current Behavior

An error message of Healthy and Unhealthy Threshold Counts must be the same.

Reproduction Steps

Create a NetworkTargetGroup with differing healthy and unhealthy threshold counts.

Possible Solution

Remove https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-elasticloadbalancingv2/lib/nlb/network-target-group.ts#L262-L268

Additional Information/Context

No response

CDK CLI Version

2.91.0

Framework Version

No response

Node.js Version

18.17.1

OS

macOS 13.5.1

Language

Python

Language Version

3.9.16

Other information

No response

[peterwoodworth]

I can't find any docs on the topic, and neither the PR or the issue it fixed linked to any docs either. I'm not sure that your CLI output shows that the values can differ. Can you use escape hatches to set the values manually and see if it deploys? Or link to docs that states the values can differ?

[toxygene]

My apologies -- I copy/pasted the output from the wrong target group. Here is the output for a target group with differing thresholds:

➜  aws elbv2 describe-target-groups --target-group-arns [omitted] --query 'TargetGroups[0].[HealthyThresholdCount,UnhealthyThresholdCount]' 
[
    5,
    2
]

Additionally, here is a screenshot of the web console:

[peterwoodworth]

Great, thanks!

[msambol]

@peterwoodworth I'll take this.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.