1 Answer
- Newest
- Most votes
- Most comments
0
Look at Proxy integrations. You need to define a greedy path using /{Proxy+}. This way you do not need to specify all routes in the API but rather specify one and let the Lambda function do the routing internally.
As an alternative you could create multiple routes and assign each one to a different function.
Relevant content
- Accepted Answerasked 8 months ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
After I added
ANY
/{proxy+}
route, every request (including the root request/
) returns{"message":"Internal Server Error"}
.I tried both
/{proxy+}
and/{Proxy+}
.Is your target invoked? If so, maybe it returns a malformed answer.