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

관련 콘텐츠