Repository navigation
fix: build Web Functions for arm64 - #9379
Merged
Merged
Conversation
Lambda Web Functions run only on arm64, but WebFunction.architecture returned x86_64, so sam build produced x86_64 native dependencies (and used the latest-x86_64 image with --use-container). Fixes aws#9378
reedham-aws
previously approved these changes
Oct 28, 2026
🧪 Hands-on test: No problems observed in 5 scenariosCommit Scenarios
🤖 Automated hands-on test — not a review approval · model claude-opus-5.5 · Kiro kiro-cli 2.33.1 · build History (2)
|
Web Functions run only on arm64, so suggest arm64 emulation or an arm64 host instead of changing the architecture in the template.
reedham-aws
approved these changes
Oct 28, 2026
Vandita2020
approved these changes
Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue(s) does this change fix?
#9378
Why is this change necessary?
Lambda Web Functions run only on arm64 (docs), but
WebFunction.architecturereturnedx86_64.sam buildtherefore produced x86_64 native dependencies (and pulled thelatest-x86_64image with--use-container), which fail to load at runtime.How does it address the issue?
WebFunction.architecturenow returnsarm64. Build graph, workflow selection, and container image selection all read this property, so no other source changes are needed. Unit tests updated.Verified with the repro from the issue (
sharpdependency,--use-container): the build usesbuild-nodejs24.x:latest-arm64, producessharp-linux-arm64, and the deployed Web Function returns{"ok":true,"arch":"arm64"}.What side effects does this change have?
Web Functions built on x86_64 hosts without
--use-containernow hit the same cross-architecture handling as anAWS::Serverless::FunctionwithArchitectures: [arm64].Mandatory Checklist
PRs will only be reviewed after checklist is complete
make prpassesmake update-reproducible-reqsif dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.