Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to deploy

See original GitHub issue

Unable to deploy to lambda when I run grunt deploy, getting following error:

Running "lambda_upload" task
Fatal error: Cannot read property 'Configuration' of null

My gruntfile is as follows:

var grunt = require('grunt');
grunt.loadNpmTasks('grunt-aws-lambda');

grunt.initConfig({
lambda_invoke: {
    default: {
      options: {
        file_name: 'index.js'
      }
    }
},
lambda_deploy: {
    default: {
        options: {
            timeout : 10,
            memory: 256            
        },
        arn: 'arn:aws:lambda:us-east-1:XXXXXXXX:function:XXXX'
    }
},
lambda_package: {
    default: {
    }
}
});

grunt.registerTask('deploy', ['lambda_package', 'lambda_deploy']);

I am able to run grunt lambda_package and get no issues. Tried running grunt lambda_deploy on its own, but to no avail.

Issue Analytics

State:
Created 8 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

pailorocommented, Sep 25, 2018

Same issue

0reactions

JackyShucommented, Dec 14, 2017

I have the same issue with ‘grunt deploy’. Double checked function name, its correct.

grunt deploy --force --stack Running “lambda_package:default” (lambda_package) task aaaaaaa@1.0.0 …/…/…/…/tmp/1513286865475.8289/node_modules/newsletter-registration Created package at ./taaaaaaaaaaa_1-0-0_2017-11-14-21-27-45.zip

Running “lambda_deploy:default” (lambda_deploy) task Warning: Unable to find lambda function arn:aws:lambda:ca-central-1:999999999999:function:zzzzzzz, verify the lambda function name and AWS region are correct. Used --force, continuing. Fatal error: Cannot read property ‘Configuration’ of null TypeError: Cannot read property ‘Configuration’ of null at Response.<anonymous> (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/utils/deploy_task.js:135:31) at Request.<anonymous> (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/request.js:354:18) at Request.callListeners (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/sequential_executor.js:105:20) at Request.emit (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/request.js:596:14) at Request.transition (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/request.js:21:10) at AcceptorStateMachine.runTo (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/state_machine.js:14:12) at /home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/request.js:37:9) at Request.<anonymous> (/home/ec2-user/slack-user-registration-notification/aws-files/node_modules/grunt-aws-lambda/node_modules/aws-sdk/lib/request.js:598:12)