1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hi, I may be wrong (I didn't test in details) but I see at least one interesting difference:
- the Secret cache is local to your Lambda execution. So, it's useful if you make several calls to SecretManager to obtain same secret multiple time during the execution of your Lambda.
- The Lambda extensions can be shared across multiple executions: so, you get the benefits of caching (less cost due to less API calls, reduced latency) multiple times.
This article shows the results across multiple executions with AWS Lambda Extension for Secrets: https://www.element7.io/2022/12/boost-performance-and-reduce-costs-using-lambda-extensions/
On https://github.com/aws/aws-secretsmanager-caching-java, the recommendation is to use the Secret Cache with
private final SecretCache cache = new SecretCache();
In this form, it will go away at the end of each Lambda execution
Best, Didier
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
I think that execution reasoning makes sense, thanks :)