-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PROPOSAL] Create a public lambda layer #724
Comments
Does this belong in opensearch-js client? Should/can it be its own repo, and if so have you tried making one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What/Why
What are you proposing?
Provide the ARN for a public Lambda layer
What problems are you trying to solve?
In many cases I am in a need of running a one time OpenSearch request on a lambda, I need to do it on a lambda because the authentication is with an assumed role, most of the the times this role is exclusive for lambdas to assume, and it's quite bothersome to run npm install every time to create the lambda zip file with all the dependencies.
I've created my own personal layer but I have to create it multiple times because I manage multiple accounts.
What is the developer experience going to be?
So in order to have the dependencies ready for a one time use, i think it would be a good idea to have public layers available,
The same way AWS Power tools does it.
https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer
The text was updated successfully, but these errors were encountered: