Skip to content
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 note for lambda x86-64v2 compatibility #44021

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/src/main/asciidoc/aws-lambda-http.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,13 @@ NOTE: If you are building on a non-Linux system, you will need to also pass in a
Lambda requires Linux binaries. You can do this by passing `-Dquarkus.native.container-build=true` to your build command.
This requires you to have Docker installed locally, however.

NOTE: According to https://docs.aws.amazon.com/linux/al2023/ug/system-requirements.html#system-requirements-cpu-x86-64[the AWS docs], AL2023
x86-64 binaries are built for the x86-64-**v2** revision of the x86-64 architecture. Quarkus defaults
https://quarkus.io/guides/building-native-image#quarkus-core_quarkus-native-march[quarkus.native.march] to x86-64-**v3**. This could cause
https://repost.aws/questions/QUBVnl6hn-Toe1LPr1qjOXzg/lambda-failed-with-java-compiled-into-machine-code[issues] if Lambda provisions older
hardware. To maximize Lambda compatibility, set `quarkus.native.march=x86-64-v2` for x86-64. See:
https://quarkus.io/guides/native-reference#work-around-missing-cpu-features[]

include::{includes}/devtools/build-native-container.adoc[]

== Extra Build Generated Files
Expand Down
Loading