1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
It is possible that the Lambda version or alias for which you are updating the settings is different, and the timeout value has not been updated.
Please make sure you are updating the correct version and alias.
https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html
Relevant content
- AWS OFFICIALUpdated 4 months ago
Wow, you nailed it. Function deployment was not picking up the extended timeout I set on the sam template. No idea why not and I have never seen this before. Thank you!