Reputation: 373
I have an application load balancer with a HTTP listener that should be invoking a Lambda.
However, there is no response when I make a request to the ALB's endpoint (This site can’t be reached
).
There is no logs in Lambda's Cloudwatch from the requests I'm making, so it seems doesn't get invoked.
I also enabled Access Logs for ALB, however the bucket only contains one file (AWSLogs/ELBAccessLogTestFile
) that was created when logging was enabled.
Additionally, I enabled health checks on the Target Group, and it's showing that the target Lambda is healthy. I can see the health check requests in Lambda's CloudWatch.
ACL allows all traffic:
There are 3 subnets associated with the ALB, they all use the same route table that does link to Internet Gateway:
So to me it looks like everything that's mentioned in the AWS troubleshooting for ALB is fine.
Other relevant settings:
Upvotes: 3
Views: 3648
Reputation: 56
Failed to connect to <> port 80: Timed out
This message indicates that the curl can't connect to the ALB, not the ALB to lambda. Your ACL and route table look good. So I'd suggest checking a security group of the ALB. It must allow traffic on port 80 from at least your IP (or from specific CIDR depending on your requirements).
Upvotes: 3