Aws-sdk-js: I am excluding aws-sdk in my webpack bundle for Lambda

[gatsbyz]

When webpacking for lambda, I am removing aws-sdk completely from the webpack bundle since lambda has it built-in. However, it seems to be throwing errors. Is there a way to specify that it needs to use the lambda's aws-sdk?

[gatsbyz]

This is a question.

[srchase]

Hello @gatsbyz,

What error are you receiving? From webpack? Or Lambda?

[gatsbyz]

@srchase Hi. If I do node index.js (the webpack output file), I get an error saying that aws-sdk doesn't exist. Since lambda has aws-sdk built in, I assumed if I upload the zipped file to lambda, it would understand it. However, I'm getting an error in Lambda CloudWatch console saying Unable to import module 'index'

[srchase]

@gatsbyz

That sounds like a zip packaging error. Are you zipping the directory instead of the contents of the directory?

Your zip file should have index.js at the top level, not inside of a directory.

[gatsbyz]

@srchase I am zipping the contents of the directory. When I zip the directory, I get an error on the AWS Console UI.

[gatsbyz]

This is what it looks like now. When I include new webpack.IgnorePlugin(/aws-sdk/) in webpack configuration, it fails. (When I take out this config, it works) Below is the CloudWatch logs.

[gatsbyz]

Logs when I upload the zip with aws-sdk in it.

[srchase]

I'm having a bit of trouble following what errors you are getting under which scenarios.

When you include aws-sdk (removing new webpack.IgnorePlugin(/aws-sdk/)), everything is working?

[gatsbyz]

@srchase Sorry for the confusion. When I ignore aws-sdk, it is failing. I assume it should work since lambda has this built in. I'm trying to reduce package size.

[srchase]

Are the directory structures the same whether or not aws-sdk is ignored? (Minus the ignored aws-sdk files).

In the first screenshot you posted, there is a build-lambda directory at the top level. Does that get added when you ignore aws-sdk?

[gatsbyz]

@srchase Yeah I just wanted to show you that zipping the directory and uploading gives me a different error than what I'm getting now. And yes, the directory IS the same in the case of having and not having aws-sdk included.

[gatsbyz]

@srchase I guess my final question is that, do I need some annotation or configuration to tell lambda to include aws-sdk from it's built-in?

[srchase]

You want to use webpack's Externals, rather than ignore.

Try adding this to your webpack config:

  externals: {
    'aws-sdk': 'aws-sdk'
  }

That will keep aws-sdk from being bundled into index.js, and will instead use lambda-provided aws-sdk instead.

[gatsbyz]

Thank you so much. You're the best. It's funny to know that it was a built-in attribute all along. Doi.

[srchase]

You're welcome! Glad this helped.

[playground]

when specify
externals: {
'aws-sdk': 'aws-sdk'
}
I'm able to build and deploy to lambda, but when invoke the function, it's throwing

{
  "errorMessage": "Cannot find module 'stream'",
  "errorType": "Error",
  "stackTrace": [
    "Array.forEach (<anonymous>)",
    "Object.e.require (/var/task/src/handler.js:16:70056)",
    "Object.<anonymous> (/var/task/src/handler.js:1:1323)",
    "n (/var/task/src/handler.js:1:186)",
    "Object.<anonymous> (/var/task/src/handler.js:16:68255)",
    "n (/var/task/src/handler.js:1:186)",
    "Object.<anonymous> (/var/task/src/handler.js:16:51436)",
    "n (/var/task/src/handler.js:1:186)"
  ]
}

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.