How to add health check request ip to load balancer security group?

0
votes

I face an issue in AWS Elastic BeanStalk health checking. I deployed to my NodeJS application to AWS via elastic beanstalk. Then I give permission my elastic load balancer TCP 443 port accessible for only my domain that is routed by Cloudflare. Basically, My elastic load balancer is only accessible by Cloudflare,

enter image description here

Due to the fact that I use Cloudflare, AWS health checks can not be able to access to the endpoint of the load balancer. How can fix this issue? I don't want to open my load balancer TCP 443 port to all world people. I want to open TCP 443 port for the only Cloudflare and, at the same time, I want to use health check of AWS :)

1
amazon-web-servicesamazon-elastic-beanstalkamazon-elbaws-security-group
You mean, the Route53's health checks? – Marcin
not Route53, health check of the elastic beanstalk. Accessible from instances section, target group, – Halil İbrahim Özdoğan
The ALB HCs are between ALB and instances. What Cloudflare has to do with them? – Marcin
@Marcin, thanks for really helpful answers. I have just made a very stupid mistake, because of that it was giving. I am going to remove question :)) – Halil İbrahim Özdoğan
You can provide an answer for your own question. Its better then deleting question. Others may have similar issues in future. – Marcin

1 Answers

1
votes

If somebody reads this question in the future, I thought that the health-check is being executed, externally - accessing publicly. But I have just learned that it was not :)). It is being executed directly internally. There is no problem related to Cloudflare or the security group or any other thing! If there is an error in your ELB regarding this, the problem is probably related to your codebase, not the security group or other configurations.