Having trouble setting environment variables for AWS Lambda using Serverless v1.4.0

Question

Following the documentation, I tried declaring environment variables in the serverless.yml file under provider:

provider:
  cfLogs: true
  name: aws
  runtime: nodejs4.3
  stage: dev
  region: eu-west-1
  profile: serverless-admin
  environmnent:
    IS_REMOTE: ${file(./config.yml):IS_REMOTE}
    REMOTE_ENV: "YES"

None of these are available to me when trying to get them using process.env.IS_REMOTE or process.env.REMOTE_ENV.

This is the log of trying to console.log them:

2017-01-01 06:22:57.777 (+02:00)        undefined       REMOTE_ENV:  undefined
2017-01-01 06:22:57.777 (+02:00)        undefined       IS_REMOTE:  undefined

This is inside Lambda when using serverless invoke (not locally).

Hope someone can help me figure this out, as it seems like I'm following the docs about right.

GeeDawg · Accepted Answer · 2018-11-15 01:59:43Z

2

From the code, it looks like environmnent is misspelt.

answered Nov 15, 2018 at 1:59

GeeDawg

5034 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 10:30:36Z

1

This feature works fine for me. I believe that you have mistyped something.

Could you please create a new project and test the following steps? Maybe we can find what is your issue through a MCVE. Give me a feedback if this code does not work for you.

Check your Serverless version (expected: 1.4.0)
```
serverless --version
```

Create a new project

serverless create --template aws-nodejs --name test-project

Use the following serverless.yml

service: test-project

provider:
  name: aws
  runtime: nodejs4.3
  environment:
    VAR_1: foo

functions:
  hello:
    handler: handler.hello

Use the following handler.js

module.exports.hello = (event, context, callback) => {

  console.log(process.env.VAR_1);

  const response = {
    statusCode: 200,
    body: JSON.stringify({
      message: process.env.VAR_1
    }),
  };

  callback(null, response);
};

Deploy
```
serverless deploy
```
Test
```
serverless invoke --function hello
```

HTTP result:

{
    "statusCode": 200,
    "body": "{\"message\":\"foo\"}"
}

Log:

2017-01-02T20:13:58.551Z    fg57ea3c-e127-11e6-bf5a-93b2958503d8    foo

edited May 23, 2017 at 10:30

CommunityBot

11 silver badge

answered Jan 2, 2017 at 20:15

Zanon

31k21 gold badges119 silver badges127 bronze badges

1 Comment

Harel Rozental Over a year ago

Hmm I actually tried to delete this question as the next day I looked at it with fresh eyes and saw my serverless.yml says environmnent instead of environment. Subtle but deadly. Since for some reason the deletion didn't go through, and you did answer with "mistyped", this is the accepted answer. Thanks

Collectives™ on Stack Overflow

Having trouble setting environment variables for AWS Lambda using Serverless v1.4.0

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related