Can't create new function in 2.0.0-alpha.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, javascript, node.js
Research direction
Reproduce deployment of a new function with node-lambda 2.0.0-alpha.0 and inspect the ResourceNotFoundException. Compare the behavior with issue #182 and pull request #757; done means a function that does not yet exist in AWS can be deployed successfully.
Written by the indexing model from the issue text.
Description
I cannot deploy an AWS Lambda function using node-lambda. After upgrading to 2.0.0-alpha.0, when I try to deploy a new function that doesn't exist yet, I get this error:
ResourceNotFoundException: Function not found: arn:aws:lambda:eu-west-1:333333:function:myService-staging
at AwsRestJsonProtocol.handleError (/home/vlad/n/lib/node_modules/node-lambda/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:891:27)
This seems related to issue #182 in the node-lambda repository, but in my case it's the opposite. I've verified my IAM permissions include "lambda:*" as suggested, and I don't have VPC settings configured. The function definitely doesn't exist in AWS yet, but node-lambda fails to create it.
Related:
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from motdotla/node-lambda
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
motdotla/node-lambda#641 · 6 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
motdotla/node-lambda#618 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
motdotla/node-lambda#544 · 1 reaction ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
motdotla/node-lambda#537 · 2 comments · 1 reaction ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
motdotla/node-lambda#531 ·
All issues in motdotla/node-lambda
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100