AWS负载平衡器 /目标组443不起作用
我有一个正在曝光端口443和端口80的容器。我创建了一个任务定义，该任务定义揭示了端口80和端口443。然后，我为HTTPS和HTTP创建了一个目标组。我设置了一个负载平衡器，该负载平衡器正在聆听创建的目标组的HTTPS和HTTP。然后，我去创建了ECS服务。该服务加载容器端口443。它要求我创建一个新的目标组，但我刚刚指出了我先前创建的HTTPS目标组。服务运行后，我去了Alb URL，并且无法暂时获得503服务。我查看了访问日志，看起来Alb正在转发到“前进” - “” - “ - ” - “” - “” - “ - ” - “ ..
有趣的是，如果我转到IP地址，在容器中，我可以同时访问：80和：443，完全没有问题。因此，很显然，我对负载平衡器的做法并不是正确的。
不确定如何解决这个问题。任何帮助将不胜感激。
I have a container that is exposing ports 443 and port 80. I created a task definition that exposes port 80 and port 443. I then created a target group for https and http. I setup a load balancer that is listening to HTTPS and HTTP for the target groups created. I then went and created a ECS service. The service loads the container port 443. It asked me to create a new target group but I just pointed at the https target group that I created previously. Once the service is running, I go to the alb url and I get a 503 Service Temporarily Unavailable. I looked at the access logs and it looks like the alb is forwarding to nowhere "forward" "-" "-" "-" "-" "-" "-"..
What's interesting is that if I go to the ip addresses of the container I can access both :80 and :443 with no problem at all. So obviously I am not doing something right with the load balancer.
Not sure how to resolve this. Any help would be greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论