- Más nuevo
- Más votos
- Más comentarios
When you change the configuration, that includes environment variables, this publishes a new version of the Lambda. The restore option given in the console is to restore a previous version. When you restore a previous version, it creates a new ARN for this new restored version because it is treated as a new version publish event.
When you publish a lambda, it becomes immutable and is a snapshot of the function code and configuration that can't be changed (except for a few configuration items relevant to a function version, such as provisioned concurrency). That's why you are getting that error.
Thank you for the answer.
I published the version manually (from $LATEST to version "1") and the notification bar disappeared. Then: 1) deployed (via CDK) some changes to it and also 2) updated the configuration manually via console, the notification bar didn't come out any more.
I'm very confused about the Lambda behavior. Why the "restore" notification showed to the configuration change on the initial function but not showed any more to it with "published version"?
Also I'd like to comment the "InternalError" got in the update function operation. Is this error not handled correctly in one of the Lambda Services? If updating configuration to an immutable snapshot is wrong, it'd be great to throw the 4xx error with detailed description explicitly.
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
Where are you seeing the message about the function being idle? I've not seen that before so looking for guidance to answer the question.
it's a sticky notification bar on the top of the Lambda function console. updated the question and attached the snapshot of the bar.