How to use with AWS Lambda (ie. w/o env vars)? #277

Activity

1. darkyen commented on May 31, 2016

   

   darkyen

   on May 31, 2016

   More actions

   @GitTom why can't you use dotenv ? .env files are supported pretty much anywhere, and it can load your environment variables to process.env.*,

   👍React with 👍1Reacted by Ole Ersoy
2. GitTom commented on Jun 1, 2016

   

   GitTom

   on Jun 1, 2016

   Author

   More actions

   Good suggestion. Looking more closely I see that node-lambda (a module for testing and deploying lambda functions) uses dotenv itself, and from it's docs it looks like it uses it to load stuff into process.env. I'm a little confused about how that jives with the assertion that lambda doesn't support environment variables which I've seen in a few places, but that's just academic now.

   http://stackoverflow.com/a/37033620/150016
3. freewil commented on Jun 10, 2016

   

   freewil

   on Jun 10, 2016

   Contributor

   More actions

   I'm using Apex, which supports using environment variables with Lambda. It just creates a small wrapper around your lambda handle that sets variables on process.env:

   try {
     var config = require('./.env.json')
     for (var key in config) {
       process.env[key] = config[key]
     }
   } catch (err) {
     // ignore
   }
   
   exports.handle = require('./index').handle

   👍React with 👍2Reacted by Ricardo Ruiz and Igor
4. thebigredgeek commented on Dec 14, 2016

   

   thebigredgeek

   on Dec 14, 2016

   Contributor

   More actions

   See #370. Closing
5. thebigredgeek

   closed this as completedon Dec 14, 2016
6. GitTom commented on Jan 19, 2017

   

   GitTom

   on Jan 19, 2017

   Author

   More actions

   For the record, AWS Lambda recently added support for environment variables.

   👍React with 👍3Reacted by freewil, Andrew E. Rhyne and Ole Ersoy
7. johnelliott commented on May 24, 2017

   

   johnelliott

   on May 24, 2017

   More actions

   @GitTom how did you specify the variables? I can't get debug to turn on regardless of what I set in the AWS console.
8. GitTom commented on May 25, 2017

   

   GitTom

   on May 25, 2017

   Author

   More actions

   @johnelliott I'm configuring debug module via the Lambda env variables. On the code tab of my lambda configuration, in "Environment variables" section, I added 'DEBUG' with value '*'.

   Looking around I see that I also have a line "DEBUG=*" in my deploy.env file for node-lambda, and then in my .env file I have "CONFIG_FILE=deploy.env".
9. johnelliott commented on May 25, 2017

   

   johnelliott

   on May 25, 2017

   More actions

   Thanks @GitTom for replying.

   I did a bit of a debug-ectomy on my function for now. I tried setting DEBUG in the AWS console as you mentioned and manually setting process.env.DEBUG in my code. Neither of those worked, so I'll have to give it another shot some time. Thanks 👍
10. hrushilok commented on Apr 27, 2018

    

    hrushilok

    on Apr 27, 2018

    Last edited by hrushilok

    More actions

    @GitTom
    how do you set environment variables from .env file in following syntax?
    aws lambda create-function \ --environment Variables= \
11. jamesarosen commented on Oct 7, 2019

    

    jamesarosen

    on Oct 7, 2019

    More actions

    For posterity: Lambda@Edge functions don't support environment variables, so dotenv or similar is the only way to go for those.