How about starting EC2 in the subnet associated with Lambda and checking if it can be accessed from EC2?
If you cannot access from EC2, it is possible that the IP address used by NAT Gateway is blocked at the connection destination.
It seems possible to implement traceroute in Node.js as well.
Yes, I tried to do that, but from ec2 I was able to connect. I did one more test. I deployed in a different environment. I use a different NAT gateway there. And the result is the same - timeout
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago