Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
API Gateway proxy braking access to Lambda
#1
I have an architecture where I have an API Gateway which invokes a Lambda Function and able to get response back. This Lambda function is supposed to communicate with some of the services that are running in my private VPC. So, I have attached my VPC to the lambda function and the subnets where my services are running. Now, I am able to get response from the services that are running in my VPC. But, I am unable to get the response from Lambda. It is throwing me 502 Internal Server Error. I am able to get the response from the resource configured at parent level in API Gateway but not for the services configured at proxy level. I even attached VPC endpoint interface for the API Gateway. Can someone suggest me how I can resolve this issue and get my API, Lambda and VPC all working together.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)