Lambda alias and deployments

Hi piergre:

We are happy to help you.

Question 1: If I change the alias version number, do I have to create a deploy for each group? Can be this done automatically when I change the alias version number or do we have to create a script that creates a deployment for each group?

Answer 2: Usually we point lambda alias to a lambda version, then that means whenever you create a new version of lambda(even through you have created a alias before), you still need to point your alias to your very last lambda version in lambda console and creates a deployment for each group.

Question 2:how can I understand which version of the lambda is deployed into the device without ssh into it

Answer 2: If you use a alias version, then without ssh into device, you can navigate to Greengrass console(IoT Core -> Greengrass on left panel -> Groups -> select <your_group> -> deployment -> lambdas)to check the alias version, but you will not see the version that this alias is pointing to, you have to go to lambda console to check which version this alias is pointing to now.

Thanks

To add to the answer for question 1, yes you do need to re-deploy the associated greengrass groups if you change the version number for a certain alias. Re-deploying the group will copy the new lambda function onto the edge device. If you do not re-deploy, it will continue using the version number that you used during the last deployment.