Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Node-lambda loses file permissions

Open
#355 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, javascript, node.js
Domain
cli, cloud

Research direction

Reproduce the deployment with a project containing an executable FFMPEG binary, then compare its permissions with a manually created ZIP uploaded to AWS. Done means node-lambda preserves the binary's execute permissions during deployment so the Lambda function can run it.

Written by the indexing model from the issue text.

Description

bug question

I have a lambda function that processes MP3s. One of the files in my project is an FFMPEG binary which requires execute permissions so that my Node code can execute it. The binary has the needed permissions on my local computer, and everything works locally, but when I use node-lambda to deploy to AWS the permissions are lost (the binary ends up with just read permission) so it can't be executed. I'm able to work around the issue by zipping this project by hand and uploading the ZIP file to AWS the old fashioned way--the needed file permissions are preserved when I ZIP it by hand.

Dominant language
JavaScript
Stars
1.4k
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.