Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

"invalid ELF header" when using the nodejs "ref" module on AWS Lambda

I've just uploaded a zip to AWS Lambda which included the "ref" (https://www.npmjs.com/package/ref), which is needed to validate an iOS Game Center authentication token (How to authenticate Game Center User from 3rd party node.js server).

Unfortunately invoking it results in the "invalid ELF header" error,

{
  "errorMessage": "/var/task/node_modules/ref/build/Release/binding.node: invalid ELF header",
  "errorType": "Error",
  "stackTrace": [
    "Module.load (module.js:356:32)",
    "Function.Module._load (module.js:312:12)",
    "Module.require (module.js:364:17)",
    "require (module.js:380:17)",
    "bindings (/var/task/node_modules/ref/node_modules/bindings/bindings.js:76:44)",
    "Object.<anonymous> (/var/task/node_modules/ref/lib/ref.js:5:47)",
    "Module._compile (module.js:456:26)",
    "Object.Module._extensions..js (module.js:474:10)",
    "Module.load (module.js:356:32)",
    "Function.Module._load (module.js:312:12)"
  ]
}

This has been developed on a 64bit Macbook Pro running Yosemite which has no problem running the code locally. Googling around for "invalid ELF header" has yielded little to know relevant results and I'm really not sure where to go from here. Would I be better asking this in a node.js area, or is this the relevant area, because it might be an issue with the platform?

like image 203
seaders Avatar asked May 01 '15 20:05

seaders


People also ask

How do I fix invalid ELF headers?

If you extracted the installer folder on a different OS, then moved it to a Linux machine, the symbolic links will not be created during the installation resulting in an "Invalid ELF header" error. The resolution is to move the installer zip file over to the Linux machine and then unzip the installer on that OS.

Does AWS lambda support node JS?

AWS Lambda now supports Node. js 16 as both a managed runtime and a container base image. Developers creating serverless applications in Lambda with Node. js 16 can take advantage of new features such as support for Apple silicon for local development, the timers promises API, and enhanced performance.


3 Answers

This happens when you build on one architecture and then attempt to use the same built addon on a different architecture (or platform in some cases).

According to this page, addons may have to be compiled against an Amazon Linux image on EC2 in order for the compiled addons to be usable on their Lambda service.

like image 68
mscdex Avatar answered Sep 27 '22 21:09

mscdex


This doesn't apply exactly to your question, but in case anyone stumbles across this when using AWS Elastic Beanstalk, it could be a result of uploading the node_modules/ directory along with everything else, so you need to force it to ignore the file.

.ebignore

node_modules/
like image 21
Matt Fletcher Avatar answered Sep 27 '22 21:09

Matt Fletcher


For those Developers porting JS to TypeScript on Lambda, ensure ALL dependancies are imported, not required:

import $ from "cheerio";

NOT

const $ = require("cheerio");
like image 32
Jason Mullings Avatar answered Sep 27 '22 21:09

Jason Mullings