Kralizek / Kralizek/AWSSecretsManagerConfigurationExtensions
Lambda Caching Layer
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 260
- Forks
- 54
- Avg merge
- 5h 56m
- Merged PRs (30d)
- 5
Description
Hello,
I'm using AWSSecretsManagerConfigurationExtensions with api running on Lambda. But i'm now facing the issue where the GetSecretValue limit of 10k read/seconds is reached.
I saw AWS provide a cache layer for secret and parameter that can be dirrectly link to a lambda function :
https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets_lambda.html
For example you can add this layer to your function with cloudformation like this :
Layers:
- arn:aws:lambda:eu-central-1:187925254637:layer:AWS-Parameters-and-Secrets-Lambda-Extension-Arm64:4
Actually AWSSecretsManagerConfigurationExtensions is reading secret at each application start. in the case of .net api running on lambda, each invocations is reading secret.
Can we imagine an implementation of the cache layer of lambda ?
Regards
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 with AWSSecretsManagerConfigurationExtensions and compare its current secret retrieval behavior with the AWS Parameters and Secrets Lambda Extension described in the linked documentation. Define how the cache layer should be enabled and used for Lambda invocations, then verify that repeated invocations no longer call GetSecretValue each time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100