skip to Main Content

I have a simple Lambda deployed into my VPC that is making a call to an EC2 host in the same VPC (and subnet). They both share an SG and I’ve used the Reachability Analyzer (from the Lambda ENI to the EC2 Instance) and it says they can talk. But when I test the Lambda it sits on the HTTPS call (the call should be very quick) and eventually the Function timesout.

Any other ways to debug the Lambda->EC2 path, if that is even the issue.

2

Answers


  1. Chosen as BEST ANSWER

    This may not apply to everyone, but my issue was a 3rd party Firewall that was fronting the ALB. To test this theory I used the direct internal IP address of the server and it worked fine.


  2. It usually sign that security group settings are blocking you.
    Here is some steps for troubleshoot:

    1. Your Security Group shouldn’t block inbound or outbound connection to itself or EC2 and rather explicitly allowing it.
    2. Check EC2 inbound rules, access to SG should be explicitly set there.
    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search