notationlabs / notationlabs/notation
Setting lambda concurrency should not be a default configuration
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- TypeScript
- Stars
- 54
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
It is possible to set concurrency limits on an AWS account, so Lambda concurrency should be defined by the user.
Contributor guide
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.
Research direction
Start by locating the default AWS Lambda concurrency configuration and the deployment entry point that applies it. Confirm how user-provided concurrency limits are represented; done means no concurrency limit is configured by default while an explicit user setting is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100