2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
2
Try to add logging to your function, or use X-Ray, to understand where the time is spent. If you put a timeout of 10 sec, and your function takes effectively 500 sec to run, it will constantly fail.
0
Without seeing the code it's difficult to troubleshoot from here. That said, if the processing duration should only be 10 seconds, why not set the timeout to 10 seconds?
If you need to find out why the Lambda function is running longer than 10 seconds, I'd suggest that you contact the support team as they have visibility into your environment and your Lambda functions.
Adding additional logging is definitely the first step to troubleshoot this, and don't forget to check the CloudWatch logs for the executions your function has already run - even without additional function-level logging, if your Lambda function as the basic logging IAM role attached, it will log function start and stop events, and errors, already.