Private API Gateway behind load balancer target group shows unhealthy

Question

I'm trying to put an endpoint attached to a private API gateway behind a load balancer as explained in the following article so that I can use custom DNS with the private API gateway.

https://georgemao.medium.com/enabling-private-apis-with-custom-domain-names-aws-api-gateway-df1b62b0ba7c

It's all set up the way he explains it but the problem is that the health checks from the target group are failing. The health checks are set to accept response codes from 200-499(a troubleshooting measure).

I can attempt to access the the endpoint IP from the VPC and get a 403 but it doesn't seem to respond from the load balancer. The target group health checks are set to check https on the traffic port but they are all timing out. This is some sort of reachability issue but I can't figure out why I can reach it but the load balancer cannot. The security group I have applied right now allows traffic from 0/0 on port 443 inbound.

Answer 1

Heyy, I have exactly the same issue, the reachability analyzer confirm the connection between the vpc endpoint eni and alb eni but health check still unhealthy

Answer 2

check that your security group allows outbound traffic and the health check path is set to "/ping" (on port 443) Hope this helps