scm_pa | 2021-04-05 19:56:27 UTC | #1
Hi all. I’m trying to troubleshoot an AWS Lambda integration data action and could use some insight. The customer set up the lambda function in their AWS account and have used the API gateway to create a URL. I set up the data action in the customers org but when I test I get back { "message": "[Lambda error] event does not contain routing information [REDACTED]", "code": "bad.request", "status": 400, "entityName": "REDACTED", "messageParams": {}, "contextId": "REDACTED", "details": [ { "errorCode": "ACTION.REMOTE_ENDPOINT" } ], "errors": [] }
Any troubleshooting suggestions are appreciated. I have not found much on the “event does not contain routing information” error in relation to AWS.
Thanks.
scm_pa | 2021-04-05 20:46:00 UTC | #2
One thing to add. The customer who set up the AWS side can execute the API from a simple html page sending an ajax request via jquery.
Thank you.
Jason_Mathison | 2021-04-07 11:41:01 UTC | #3
Hi scm_pa,
I am by no means an expert, but based on googling this error I have a guess what the issue is. When the lambda is run from API gateway there is going to be a route included in the lambda invocation. For example, if you are calling something like
GET https://foo.com/some/test/endpoint
The lambda invocation will include something about the lambda being called for the some/test/endpoint route.
On the other hand, when the lambda is called by the data action there is no concept of a route, so no route would be included. My guess is that the developer of the lambda will need to make a change so that it can be called without a route by a data action. It also might be possible to specify a route in the data action, but I can't provide any advice on how you would do that.
--Jason
system | 2021-05-08 11:41:02 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 10498