AWS Lambda: Support 64-bit ARM architecture #10049
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10049 +/- ##
=======================================
Coverage 85.75% 85.75%
=======================================
Files 333 333
Lines 13435 13439 +4
=======================================
+ Hits 11521 11525 +4
Misses 1914 1914
Continue to review full report at Codecov.
|
medikoo
force-pushed
the
1004-lambda-arch
branch
from
f1ea9a8
to
e3b54fb
Compare
| ```yml | ||
| provider: | ||
| ... | ||
| arch: arm64 |
There was a problem hiding this comment.
| arch: arm64 | |
| architecture: arm64 |
The word isn't really long so we might as well be explicit for clarity? Additionally the CloudFormation setting is Architectures, not Arch/Archs so we gain a bit in consistency.
There was a problem hiding this comment.
I actually followed the spec from the issue, which was confirmed as accepted.
Anyway I also thought about that, and I agree that using architecture is probably better
There was a problem hiding this comment.
👍 ok I understand better, I thought the original post (top comment of the issue) was just a suggestion. So I'm guessing for anything discussed on GitHub the practice is to discuss and update the top comment?
There was a problem hiding this comment.
Yes, issue serves as specification then
medikoo
force-pushed
the
1004-lambda-arch
branch
2 times, most recently
from
662f26f
to
44c9174
Compare
|
|
||
| By default, Lambda functions are run by 64-bit x86 architecture CPUs. However, using arm64 architecture (AWS Graviton2 processor) may result in better pricing and performance. | ||
|
|
||
| To switch all lambdas to AWS Graviton2 processor, configure `arch` at `provider` level as follows: |
There was a problem hiding this comment.
Maybe let's write all functions instead of all lambdas?
medikoo
force-pushed
the
1004-lambda-arch
branch
2 times, most recently
from
2811a10
to
589217e
Compare
@pgrzesik very good point, added |
| @@ -597,6 +599,9 @@ layers: | |||
| description: Description of what the lambda layer does # optional, Description to publish to AWS | |||
| compatibleRuntimes: # optional, a list of runtimes this layer is compatible with | |||
| - python3.8 | |||
| compatibleArchitectures: # optional, a list of architectures this layer is compatible with | |||
There was a problem hiding this comment.
It would be great to add a reference to this setting in layers.md documentation
There was a problem hiding this comment.
Good point @pgrzesik Added
medikoo
force-pushed
the
1004-lambda-arch
branch
from
589217e
to
9cfba13
Compare
Closes: #10025
Additionally cleaned up lambda based fixtures, to create better room for the testing general lambda related enhancements