We need access to the value of COMMIT_REF from our (Node.js) lambda functions. This works locally since the value is accessible directly in process.env. However, once deployed this doesn’t work anymore. I’ve looked at the proposed solutions to have acces to the build variables, but they’re all fo…

Accessing build environment variables from lambda functions

miShelbyT December 20, 2022, 10:24pm 5

Hi @PabloRomanH I don’t know if this will help but I had a similar issue that was solved by setting an env variable for the AWS node.js version (which defaults to 16.x). Worked like magic! Hopefully it will solve your issue as well.

Topic		Replies	Views
Netlify function environment variables returning undefined Support deployment , lambda-functions , environment-vars	1	1084	November 18, 2019
How to access Netlify Continuous Deployment Pre-Defined Env. Variables in client side JS? Support lambda-functions , environment-vars	12	3889	October 14, 2019
NODE_ENV is undefined in lambda functions no matter what I do Support lambda-functions	11	5903	January 27, 2021
AWS_LAMBDA_JS_RUNTIME - nodejs14.x Support lambda-functions	7	3369	July 1, 2022
Access environment variables outside of functions? Support netlify-dev-open-beta , environment-vars	7	2996	May 29, 2020

Accessing build environment variables from lambda functions

Related topics