Health check paths are not supported for TCP health checks

Question

I've been trying to create an elastic beanstalk environment, and I keep getting an error when eb tries to create the target group.

```
Creating target group failed Reason: Resource handler returned message: "Health check paths are not supported for TCP health checks (Service: ElasticLoadBalancingV2, Status Code: 400, Request ID: xxxxxxxx)" (RequestToken: xxxxxx, HandlerErrorCode: InvalidRequest)
```
If health check paths aren't allowed for TCP [health checks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-targetgroup.html#aws-resource-elasticloadbalancingv2-targetgroup-properties) , then what are you supposed to do since the default is set to / and the required length is 1 so you can't set it to empty?

Here is the part of my eb configuration that pertains to the nlb:

```
option_settings:
  aws:elbv2:listener:443:
    ListenerEnabled: "true"
Resources:
  AWSEBV2LoadBalancer:
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    Properties:
      Scheme: internal
      Subnets:
        - subnet-xxxx
        - subnet-xxxx
        - subnet-xxxx
      Type: network
  AWSEBV2LoadBalancerListener:
    Type: AWS::ElasticLoadBalancingV2::Listener
    Properties:
      Port: 443
      Protocol: TCP
  AWSEBV2LoadBalancerTargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      Port: 443
      Protocol: TCP
      VpcId: vpc-xxxx

```

Answer

I ended up just switching the the health check to HTTPS on port 443, which removed the original problem. If anyone has the answer to the original problem and why that was happening though I'd still love to know.

Answer

In the link you shared it says that HealthCheckPath is not required so I'm not sure why you think it is required.

It also doesn't make sense in the context of TCP health check because the path is related to the HTTP(S) request.

Health check paths are not supported for TCP health checks

Conteúdo relevante