2 Answers
- Newest
- Most votes
- Most comments
0
Finally solved it by adding an inbound rule to the Lambda's ENI security group allowing all traffic from all protocols & ports from 10.0.0.0/16
answered 3 months ago
0
One way to troubleshoot this would be to put an EC2 instance on the same subnet that the Lambda function is connected to. That way you can test interactively what is happening. I suspect there is an issue with routing, NACLs or something else at the network layer but there's not enough information to say for sure.
Relevant content
- asked a year ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
Finally solved it by adding an inbound rule to the Lambda's ENI security group allowing all traffic from all protocols & ports from 10.0.0.0/16