2 Answers
- Newest
- Most votes
- Most comments
1
Hello,
For the ALB, was it set up as Internal or Public Facing? If it's public facing, you will need to add a NAT Gateway to the VPC to allow the Lambda to access it even though both are in the same VPC.
If the ALB is set up as Internal, ensure that the Lambda is able to access the ALB's security group. The security group assigned to the ALB may not allow the Lambda access and it will need to be added to the SG.
0
I did a mistake on my end, under terraform for LB the internal was set as false. Which made it internet-facing instead of internal and under private subnets.
answered 4 years ago
Relevant content
asked a year ago
- AWS OFFICIALUpdated 4 years ago
In my scenario, the ALB is set up as internal. I had added Lambda's SG as the source to the ALB's SG but still was getting time out while trying to reach ALB from Lambda.
I have the same issue - a VPC-joined Lambda that cannot access the ALB. I've checked the ALB SG, and also tested that I can reach other EC2 resources from a test Lambda function. But the ALB just times out (doesn't seem to return any result, even a 403). Maybe I need to confirm the H-ENI bound to the Lambda - how would I do this?