Can not start up on aws lambda.

[ryota8bit]

The following error appears and can not be started.

{
  "errorMessage": "libdns_sd.so.1: cannot open shared object file: No such file or directory",
  "errorType": "Error",
  "stackTrace": [
    "Object.Module._extensions..node (module.js:597:18)",
    "Module.load (module.js:487:32)",
    "tryModuleLoad (module.js:446:12)",
    "Function.Module._load (module.js:438:3)",
    "Module.require (module.js:497:17)",
    "require (internal/module.js:20:19)",
    "Object.<anonymous> (/var/task/node_modules/mdns/lib/dns_sd.js:24:20)",
    "Module._compile (module.js:570:32)",
    "Object.Module._extensions..js (module.js:579:10)"
  ]
}

Can not aws run with lambda?

[kokarn]

No, you have to run it on your local network.

[noelportugal]

This won't work on AWS Lambda (or any serverless/cloud host), and it's by design rather than a bug: the library discovers and talks to your speakers over your local network — mDNS discovery + a direct Cast connection to the device's LAN IP. A Lambda function isn't on the same network as your Google Home, so it can't reach it.

Run it on something on your home LAN instead — a Raspberry Pi, NAS, or always-on PC. (You can still trigger it from the cloud by hitting the example/example.js HTTP listener via ngrok/webhook, but the notifier process itself has to live on your network.)