AWS IoT Thing running deprecated Lambda runtime (NodeJS 12.x)

Your client is facing a challenging situation with their AWS IoT Greengrass v1 deployment using the deprecated Node.js 12.x runtime. Here's an overview of the situation and potential solutions:

1. AWS IoT Greengrass v1 status: It's important to note that AWS IoT Greengrass Version 1 has entered the extended life phase and is no longer receiving updates. This means that continuing to use v1 may pose increasing risks over time.

2. Lambda runtime support: While the edge devices can still run Node.js 12.x, creating or updating Lambda functions with this runtime in AWS Lambda is no longer possible. This creates a dilemma for updating the existing functions.

3. Possible solutions:

a. Runtime override: There is a potential workaround using the FunctionRuntimeOverride parameter in the FunctionDefinitionVersion. This allows you to specify a runtime that differs from the one specified in AWS Lambda. You could potentially use this to maintain Node.js 12.x on the devices while updating the Lambda function code.

b. Upgrade runtime: Consider upgrading the Lambda functions to a supported Node.js runtime (e.g., Node.js 18.x). This would require ensuring code compatibility and potentially updating dependencies.

c. OTA update: If you can successfully update the Lambda functions (either through runtime override or upgrading), you should be able to deploy these changes via OTA updates. However, be aware that OTA updates have some implications, such as core device shutdown during the update and potential loss of data in long-lived Lambda functions.

4. Long-term considerations: While the above solutions might provide temporary relief, the client should seriously consider migrating to AWS IoT Greengrass v2 in the near future. This would ensure they receive the latest features, security updates, and runtime support.

5. Migration planning: If upgrading to Greengrass v2 becomes necessary, careful planning can help minimize the need for physical access to all devices. This might involve:

• Preparing a migration strategy that leverages OTA updates as much as possible
• Identifying which devices absolutely require physical access
• Exploring options for remote management and updates

In conclusion, while there are potential short-term solutions to update the Lambda functions, the client should start planning for a migration to AWS IoT Greengrass v2 to ensure long-term sustainability and support for their IoT deployment.
Sources
Run Lambda functions on the AWS IoT Greengrass core - AWS IoT Greengrass
OTA updates of AWS IoT Greengrass Core software - AWS IoT Greengrass
Lambda runtimes - AWS IoT Greengrass