You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion, In this case, a single layer makes more sense. As we don't have too many unshared heavy dependencies.
So keeping it common will have benefits of simplicity and less build time. and splitting it will not reduce the package size that much.
We can check if there is a substantial size reduction in the build-file after splitting.
Currently in deploy workflow, We are packaging single lambda layer
python.zip
which may be different for different lambdas.The text was updated successfully, but these errors were encountered: