[Feature request] Executing TCP/IP dependency module from Lambda layer.

[zachjonesnoel]

Installed net-ping v1.2.3 from npm and created a Lambda layer, when executing this from AWS Lambda function, getting the below error -

{
  "errorType": "Error",
  "errorMessage": "/opt/nodejs/node_modules/raw-socket/build/Release/raw.node: invalid ELF header",
  "trace": [
    "Error: /opt/nodejs/node_modules/raw-socket/build/Release/raw.node: invalid ELF header",
    "    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1131:18)",
    "    at Module.load (internal/modules/cjs/loader.js:937:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:778:12)",
    "    at Module.require (internal/modules/cjs/loader.js:961:19)",
    "    at require (internal/modules/cjs/helpers.js:92:18)",
    "    at Object.<anonymous> (/opt/nodejs/node_modules/raw-socket/index.js:4:11)",
    "    at Module._compile (internal/modules/cjs/loader.js:1072:14)",
    "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)",
    "    at Module.load (internal/modules/cjs/loader.js:937:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:778:12)"
  ]
}

I understand this limitation from the forum but raising a feature request for allowing the same on Lambda into the future.