1 Answer
- Newest
- Most votes
- Most comments
1
Nevermind, turns out the API Gateway timeout was actually lower than the timeout field showed, as I didn't redeploy the API after changing the timeout.
answered 5 years ago
Relevant content
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago