title: ECS Fargate + Network Load Balancer Healthcheck
body: <p>I'm experiencing an issue with the following setup:</p>
  
  <p>API Gateway -> VPC Link -> Private NLB -> Target Group -> AWS ECS Fargate</p>
  
  <p>If I setup the NLB's Health Check to be TCP/HTTP on a specified endpoint, that endpoint gets hammered to the death with internal request (no requests are coming through the API Gateway, I checked):
  <a href="https://i.stack.imgur.com/NuCUz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/NuCUz.png" alt="Relevant picture, note the delay between Health Checks"></a></p>
  
  <p>My problem with this behaviour, other than having the health's endpoint spammed by my own architecture is that the application's functionality is suffering (I keep getting slow responses 1 out of 4 get request to the API).</p>
  
  <p>I  tried to modify the Health Check's behaviour to only TCP, same slow responses.</p>
  
  <p>I tried temporarily switching to a public ALB, I'm incurring in double health-checks, separated by 30 seconds but my application is responding with an average of 100 ms.</p>
  
  <p>So, as an example of what I mean by "double health-checks": </p>
  
  <p>Health Check 1.1 at 00:00:00</p>
  
  <p>Health Check 2.1 at 00:00:10</p>
  
  <p>Health Check 1.2 at 00:00:30</p>
  
  <p>Health Check 2.2 at 00:00:40</p>
  
  <p>Any ideas?</p>