title: AWS Global Accelerator in front of ALB managed with EKS alb ingress health checks fail
body: <p>got an EKS cluster with alb ingress controller and external DNS connected to route53, now some clients want static IPs or IP range for connecting to our servers and whitelisting these IPs in their firewall.</p>
  
  <p>Tried the new AWS Global Accelerator, followed this tutorial <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/getting-started.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/global-accelerator/latest/dg/getting-started.html</a> but it fails with :</p>
  
  <pre><code>Listeners in this accelerator have an unhealthy status. To make sure that Global Accelerator can run health checks successfully, ensure that a service is responding on the protocol and port that you specified in the health check configuration. Learn more
  </code></pre>
  
  <p>With further reading understood that the healthchecks will be the same configured at the ALB, also that it might fail because of the route53 Healthchecks ips are not whitelisted but all the inbound traffic is open in ports 80 and 443, so not quite sure how to further debug this or if there is any other solution for getting an ip range or static ip for the ALB. </p>