2 Answers
- Newest
- Most votes
- Most comments
0
Any logs from your NLB?
Any Acls blocking this? What listener ports do you have on your NLB?
Is the ALB showing available on the NLB in the spoke VPC? Any reason why you are not using alb to alb? Why have an NLB?
Does ALB 2 security groups allow access from NLB?
0
listener ports ; 443 Since NLB is listening on TCP rule - there are no Access log created.
Also, the issue is intermittent. Out of 100 approx 15 requests gives 502 response.
We had to use NLB - because ALB1 requires a static IP address to establish connection between 2 VPCs. Out of 2 options - either using NLB or using Lambda function to watch the DNS records - we chose to use NLB.
Targets for all 3 load balancers are always in healthy state. There is not a single failure
answered a year ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago