1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
2
Lambda functions can be in one of several states. This happens during function creation and update.
I assume your API is configured to invoke a specific lambda alias. It seems you are moving your alias before the new lambda version is in the Active state. You should be update the alias only after the function gets into the Active state.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Yes, that would make sense. I have added the following commands before I update the alias pointer, and it seems to clear up the issue: