应用程序负载平衡器在网络负载平衡器面前
我有一个有公众和私人子网的VPC。我希望我的自动扩展应用程序居住在私人子网中，因此我需要通过公共子网中的负载平衡器访问它们。这些应用程序还需要在内部进行交谈。
我正在尝试使用Elastic Beanstalk在我的私有子网中创建内部网络负载平衡器，该子网指向我在私有子网中的应用程序。然后，我在我的公共子网中手动创建了一个公共应用程序负载平衡器。但是看来我的应用程序负载平衡器正在努力驶向我的网络负载平衡器。
这是合理的设置吗？我已经看到了许多公共面向网络负载平衡的示例，这表明内部应用程序负载平衡器，但不相反。我已经能够使它工作，但是我无法将HTTP重定向到网络负载平衡器的HTTP，这就是为什么我更喜欢相反的原因。如果没有其他东西，我想在公共网络负载均衡器前面的公共网络负载平衡器面前将云饰面放在前面，然后处理TLS并从Cloudfront中重定向。
谢谢
I have a VPC with a public and a private subnet. I want my auto scaling applications to live in the private subnet, so I'll need to access them via a load balancer in the public subnet. These applications also need to talk to each other internally.
I'm trying to use Elastic Beanstalk to create an internal network load balancer in my private subnet, which is pointing to my applications in the private subnet. Then I have manually created a public application load balancer in my public subnet. But it seems that my application load balancer is struggling to route to my network load balancer.
Is this a reasonable set up? I've seen lots of examples of a public facing network load balancing which is pointing to an internal application load balancer, but not the other way around. I've been able to get that to work but I can't redirect http to https at the network load balancer which is why I'd prefer it the other way around. If nothing else I'm thinking to have CloudFront in front of a public, network load balancer in front of a private network load balancer, and then handle the TLS and redirect from CloudFront instead.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不幸的是，这不是合理的设置，因为AWS不支持它。应用程序负载平衡器无法将流量转发到另一个负载平衡器。
从您的描述中不清楚为什么您需要一个指向另一个负载平衡器的负载平衡器。您的后端服务可以属于多个目标组，因此多个负载平衡器可以将流量直接转发到您的服务。换句话说，公共负载平衡器可以直接转发到您的私人服务，而无需通过私人负载平衡器。
Unfortunately no, that is not a reasonable setup, because it is not supported by AWS. An application load balancer can not forward traffic to another load balancer.
It's unclear from your description why you need a load balancer pointing at another load balancer at all. Your backend service can belong to multiple target groups, so multiple load balancers can forward traffic directly to your service. In other words, the public load balancer can forward traffic directly to your private services, without going through the private load balancer.