- Newest
- Most votes
- Most comments
This could be related to https://forums.aws.amazon.com/thread.jspa?messageID=949152󧮠
I'm having this same problem. It started yesterday and it only happens with one lambda function. Other lambda functions are deployed just fine.
I also noticed that the ci/cd tool is using an old version of the AWS SDK (1.11.834), and if I deploy the code using AWS CLI (2.2.37) it works. Could this be related?
Edited by: raulbarreto-delivion on Sep 16, 2021 7:11 AM
AWS are rolling out this change
https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/
You need to put a check for the function state in between the update_function_code and the publish version calls
Make sure the state is active before proceeding
https://docs.aws.amazon.com/lambda/latest/dg/functions-states.html
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 3 months ago