2回答
- 新しい順
- 投票が多い順
- コメントが多い順
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
回答済み 4ヶ月前
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.
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 7ヶ月前
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