I have attached VPC and private subnets in Lambda function. That is causing the connection issue with the API Gateway/other AWS services. Can anyone suggest the solution for this?

Thank you.

  • 1
    Hi Gayathri K, if the response below answered your question please upvote and accept it. That's the ServerFault's way to say thank you for the time and effort someone took to help you. Thanks!
    – MLu
    Nov 3 '18 at 3:47

I suspect it’s one of these issues:

  • If the subnet is “private” it doesn’t have a NAT gateway attached, or

  • If the subnet is “public” with IGW attached (IGW = Internet Gateway) but doesn’t have Auto-assign public IP enabled.

  • It could also be a routing issue - make sure the Route Table for your subnet has a route for pointing towards the IGW or NAT gateway.

Hope that helps :)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.