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
Historically lambda team updated the python/boto3 sdk in lambda, since q3/q4 last year they seemed to have moved away from it. Unfortunately for projects using python with newer aws services or features that causes a bit of a disconnect as they may work locally they won't in lambda without packaging up the sdk. Having lots of users do that across lots of functions seems a bit wasteful. As an alternative, it would be nice if boto3 releases were automatically released as a lambda layer in addition to the pypi release.
The text was updated successfully, but these errors were encountered:
kapilt
changed the title
add a lambda layer release artifact for a boto3
add a lambda layer release artifact for boto3
Apr 23, 2019
Would building a layer and maintaining it be the easiest way to manage keeping the boto3 version current for multiple development teams? I'm happy to do this in the interim, but would love the boto3 version stay current for the lambda runtime.
Historically lambda team updated the python/boto3 sdk in lambda, since q3/q4 last year they seemed to have moved away from it. Unfortunately for projects using python with newer aws services or features that causes a bit of a disconnect as they may work locally they won't in lambda without packaging up the sdk. Having lots of users do that across lots of functions seems a bit wasteful. As an alternative, it would be nice if boto3 releases were automatically released as a lambda layer in addition to the pypi release.
The text was updated successfully, but these errors were encountered: