-
Notifications
You must be signed in to change notification settings - Fork 138
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
Feature request: arm64
support for Lambda Layers
#1374
Comments
This is blocking for me using the layers, unless I wanted to switch away from |
Hi @codyfrisch at the moment we don't list With that said however I can confirm that at the time of writing none of the utilities we publish uses any binaries nor architecture specific dependency. This means that in principle it should be possible to use our Lambda layer on functions using However I understand the importance of having an official confirmation from our side, so we'll try to address this as soon as we can. |
|
This is now released under v1.14.0 version! |
Just to clarify the message above, what was included in the 1.14.0 tag are the integration tests that allow us to test our code on both As mentioned in the linked PR, we want to take some time to run tests over time before officially certifying that the Lambda Layers work with functions using that architecture. Nevertheless, the passing tests are an indication that we are going in the right direction. |
Use case
Currently our public Lambda Layers are tested and confirmed to work on Lambda
x86_64
architecture. Given the performance benefits that Graviton 2 can bring in some use cases, it would be great to explore compatibility with thearm64
architecture and then eventually deploy the Layers in the regions that support it.Solution/User Experience
Customers using
arm64
should be able to use the Layers. Not sure at this stage if we need a dedicated build for that architecture or the same/current layer build would work also on ARM.Alternative solutions
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: