According to the [blog post](https://aws.amazon.com/blogs/networking-and-content-delivery/application-load-balancer-type-target-group-for-network-load-balancer/), you will be able to configure single ALB as a target in NLB. So what will be the required design if the target ALB has port redirection scenario like 80 to 443?

Using PrivateLink NLB to ALB Port Redirection

According to the blog post, you will be able to configure single ALB as a target in NLB. So what will be the required design if the target ALB has port redirection scenario like 80 to 443?

主题

计算网络和内容交付

标签

计算 AWS 专用链接应用程序负载均衡器网络负载均衡器

语言

English

cnnn

已提问 2 年前866 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

Because NLB is only using a single TCP port (443 - HTTPS) to communicate with the ALB the redirect can't be done on the ALB. I'd recommend using CloudFront instead so that the 80->443 redirect happens before it hits the load balancer.

专家

Brettski-AWS

已回答 2 年前

cnnn
2 年前
Where do you put the CloudFront if you refer the below diagram? https://lucid.app/lucidchart/eb7dbf0a-5d99-42e6-9bc7-15d5856b3f2c/edit?invitationId=inv_d678e922-fabe-44b1-a708-e6c7837c2ad6
AWS-User-3043836
2 年前
I also have the same question. In our case when we start doing redirection in our ALB from http - 80 to https - 443 then this results in a loop and fails with ERR_TOO_MANY_REDIRECTS.

Using PrivateLink NLB to ALB Port Redirection

相关内容