1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hello,
it looks like in the logs you're invoking the function mysampleapi1
possibly. However it appears that its still having a function timeout.
I tested creating a scenario where my function would timeout, and I received the same type of error message. So two things may be occuring here:
- you may be invoking the incorrect API
- your Lambda function may be timing out
Granted it may be something entirely else occurring such as it could be something specific to Docker. If you can, mind sharing this issue on the AWS SAM CLI Github repo? The developers over there come across many types of issues with using the SAM CLI and may be able to quickly find a solution outside of the items I mentioned above. Here's a link to raise a question with the team: https://github.com/aws/aws-sam-cli/issues
Contenuto pertinente
- AWS UFFICIALEAggiornata 5 mesi fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
After launching my lambda in separate processes, I discovered that there's an issue in my configuration for the second service.
The issue still occured after this launcher
I noticed when I exported my configuration, for one of the services, there's the following in the
template.yaml
without the proxy line, the lambda handler just never gets called for some reason