Monitoring Visibility Impacted for AWS Lambda Layers on Node.js 22

Update timeline

1. investigating Aug 20, 2026, 09:10 PM UTC

   We are aware of an issue resulting in a loss of monitoring visibility for Lambda functions on Node.js version 22. Our team is actively investigating this issue and are working towards mitigation. We understand the importance of reliable monitoring and will provide the next update within the next four hours, or sooner if additional information becomes available. Thank you for your patience and understanding.

2. investigating Aug 20, 2026, 11:05 PM UTC

   We are actively investigating an issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. We recommend that customers avoid running nodejs:22.version 95 while our teams continue to assess scope, impact, and the path to mitigation. As an interim mitigation, customers may roll back to their previously working Node.js 22 runtime version. If assistance is needed to perform the rollback, please engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience

3. identified Aug 21, 2026, 12:01 AM UTC

   We have identified the issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. Classic Lambda layers do not work correctly with the newest AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. To avoid this impact, we recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are affected, you can roll back to the previously working Node.js 22 runtime (for example, v91). If assistance is needed to perform the rollback, customers should engage AWS Support. Our teams are working on a permanent fix and will continue to share updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

4. identified Aug 21, 2026, 08:04 AM UTC

   We continue to work on the identified issue affecting Lambda functions running on the AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. We are actively working with AWS towards a permanent fix. In parallel, our teams are investigating additional mitigation options to help reduce customer impact. As a precaution, we continue to recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are experiencing issues, you may roll back to a previously working Node.js 22 runtime version (for example, v91). Customers requiring assistance with a rollback should engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

5. monitoring Aug 21, 2026, 08:05 PM UTC

   We have identified the root cause of the issue affecting monitoring visibility for Lambda functions running on the AWS-provided Node.js 22 runtime (nodejs:22.mainline.v95), and mitigations have been applied. A fix has been released in OneAgent 1.343 for SaaS environments. Investigation into fixes for additional supported versions is ongoing. We will provide updates as they become available. As an interim workaround, customers can continue to pin their Lambda runtime to a previously working Node.js 22 version (e.g., v91). Customers requiring assistance with a rollback should engage AWS Support. We will continue to monitor the situation closely over the weekend and provide a further update once more information is available. We appreciate your patience as we work to fully resolve this issue.