-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add support for selecting Architecture to Deploy function to #1808
Comments
Should be pretty straightforward to plumb through the architecture config option, but we'll need to update the packager to handle binary python package dependencies. I'm not sure how many projects are publishing ARM wheel files. |
Is this something that will be available soon? thanks |
Is this on your roadmap or should I be looking at an alternative approach? Thanks |
Is there any update on this issue? |
Any updates here? |
Any updates here? |
Any updates? |
1 similar comment
Any updates? |
Any Updates? |
Is this on the roadmap? Our Chalice apps are the only apps we have still running on x86 instead of ARM. Is there a workaround if this isn't planned? |
+1 |
1 similar comment
+1 |
AWS began supporting Graviton2 processors today:
https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/
It would be great if we could select the architecture we want to deploy the code we are using to in the config.json file.
The text was updated successfully, but these errors were encountered: