AWS Lambda Function is returning "Cannot find module 'index'" yet the handler in the config is set to index

Question

As my title explains I am getting the following error:

 {
  "errorMessage": "Cannot find module 'index'",
  "errorType": "Error",
  "stackTrace": [
    "Function.Module._resolveFilename (module.js:338:15)",
    "Function.Module._load (module.js:280:25)",
    "Module.require (module.js:364:17)",
    "require (module.js:380:17)"
  ]
}

I have tried both solutions provided in creating-a-lambda-function-in-aws-from-zip-file and simple-node-js-example-in-aws-lambda

My config currently looks like:

and my file structure is:

and my index.js handler function looks like :

exports.handler = function(event, context) {

What else could be causing this issue aside from what was stated in those two answers above? I have tried both solutions and I have also allocated more memory to the function just incase thats why it couldn't run.

EDIT - For the sake of trying, I created an even simpler version of my original code and it looked like this:

var Q = require('q');
var AWS = require('aws-sdk');
var validate = require('lambduh-validate');
var Lambda = new AWS.Lambda();
var S3 = new AWS.S3();




theHandler = function (event, context) {

  console.log =('nothing');

}

exports.handler = theHandler();

And yet still does not work with the same error?

Having exactly the same issue.... with error `Cannot find module '/var/task/index'` during lamdba bootstrap. Thanks for asking the question! — LeOn - Han Li, Jan 26 '17 at 14:51

score 71 · Accepted Answer · answered Sep 11 '15 at 12:17

71

Try zipping and uploading the contents of the folder lambda-create-timelapse. Not the folder itself.

answered Sep 11 '15 at 12:17

tahsintahsin

994
8
18

4

Im not sure this really answers the question. Perhaps you could give a bit more detail (as to why this is a provisioning rather than coding issue) – Stuart Siegler Sep 11 '15 at 12:44
This was actually the solution I ended up using on my own. Its very annoying how amazon words this, so it wasn't easy to realize! – Andrew Font Sep 15 '15 at 14:49
4

As official documents say, at the end of the page you can see Important: you zip the folder content, not the folder itself http://docs.aws.amazon.com/lambda/latest/dg/walkthrough-s3-events-adminuser-create-test-function-create-function.html – tahsintahsin Sep 28 '15 at 08:13

score 23 · Answer 2 · answered Jan 06 '16 at 19:03

If this was unclear for anyone else, here are the steps:

Step 1 Navigate to the folder of your project, and open that folder so that you are inside the folder:

Step 2 Select all of the images you want to upload into to Lambda:

Step 3 Right-click and compress the files you have selected:

This will give you a .zip file, which is the file you need to upload to Lambda:

There are a lot of ways to automate this, but this is the manual procedure.

Amazing!!! saved me a lot of time – Charbel B.G. Mar 31 '23 at 05:50 — Charbel B.G., Mar 31 '23 at 05:50

score 12 · Answer 3 · answered Oct 09 '16 at 00:36

12

I ran into this problem a few times myself, and this indeed has to do with zipping the folder instead of just the contents like you're supposed to.

For those working from the terminal...

While INSIDE of the directory where the .js files are sitting, run the following:

zip -r ../zipname.zip *

The * is instructing the client to zip all the contents within this folder, ../zipname.zip is telling it to name the file zipname.zip and place it right outside of this current directory.

answered Oct 09 '16 at 00:36

Michael Du

669
7
15

1

Upvoted for providing clear instructions on the correct way to zip the files. – Master of Ducks Sep 17 '19 at 00:22
By default, the handler for nodejs applications is expected to be in a file called "index.js" – DrMcCleod Sep 30 '22 at 09:59
This solved the problem for me after experiencing a lot of trouble packaging my Lambda function. – Paul Wenzel Jan 11 '23 at 23:39

score 2 · Answer 4 · answered Jul 28 '15 at 03:45

2

I had the same problem sometime ago - I reformatted the code.

function lambdafunc1(event, context) {
...
...
...
}

exports.handler = lambdafunc1

answered Jul 28 '15 at 03:45

Naveen Vijay

15,928
7
71
92

score 2 · Answer 5 · answered Mar 28 '18 at 18:02

2

The problem occurs when the handler cannot be located in the zip at first level. So anytime you see such error make sure that the file is at the first level in the exploded folder.

To fix this zip the files and not the folder that has the files.

answered Mar 28 '18 at 18:02

Sushil Ojha

21
1

score 0 · Answer 6 · answered Jul 28 '15 at 16:58

0

Correct Lambda function declaration can look like this:

var func = function(event, context) {
   ...
};

exports.handler = func;

You may have other syntax errors that prevent the index.js file from being properly ran. Try running your code locally using another file and using the index.js as your own module.

answered Jul 28 '15 at 16:58

adamkonrad

6,794
1
34
41

Did not work for me, I have other lambda functions working without this change so I am not sure this is the issue.. – Andrew Font Jul 30 '15 at 20:56
You need to provide more information. What you've described can either be something very trivial or some other error. – adamkonrad Jul 30 '15 at 21:01

score 0 · Answer 7 · answered Nov 30 '19 at 20:30

0

make sure in your handler following code added

exports.handler =  (event, context, callback) => {
...
}

answered Nov 30 '19 at 20:30

vaquar khan

10,864
5
72
96

score 0 · Answer 8 · answered Jan 04 '23 at 14:30

0

Another reason this can occur is if you don't do an npm install in the folder before packaging and deploying.

answered Jan 04 '23 at 14:30

E Brake

151
5

AWS Lambda Function is returning "Cannot find module 'index'" yet the handler in the config is set to index

8 Answers8

Linked