AWS LB访问EC2进行health check的问题

最新推荐文章于 2024-08-29 15:24:43 发布

iteye_4120

最新推荐文章于 2024-08-29 15:24:43 发布

阅读量1.1k

点赞数

分类专栏：云计算文章标签： java

本文链接：https://blog.csdn.net/iteye_4120/article/details/82400438

版权

云计算专栏收录该内容

11 篇文章 0 订阅

订阅专栏

为了在AWS上面建立一套int环境，我们起了一些instance。为了系统安全，我们通过security group限制只有内部ip才能够访问。但是当我们启动一个LB的时候，无论如何都不能health check成功。通过查看网上的文章，竟然是security group限制了LB的访问！

In an ongoing effort to keep my company’s servers as secure as possible I decided I was going to lock down port 80 and 443 to only accept traffic from specific servers that needed access. Should be easy enough I thought, I could simply setup up the security group and restrict the source IP or group. I setup a test EC2 instance and ran a quick test pointing directly to the instance and it worked. I then added the rules to the production security group and thought all was well. Not so fast … I failed to remember that the Elastic Load Balancer (ELB) needs to perform health checks on each instance to confirm they are running. The problem here is you cannot tell what IP address the ELB is using to add to the security group and you cannot assign a security group to the ELB.