Describe the bug
Impossible to run a native image on AWS Lambda
Expected behavior
No error should arise
Actual behavior
The custom runtine seems not to be supported by AWS Lambda. It works well on classic EC2
To Reproduce
Steps to reproduce the behavior:
Configuration
# Add your application.properties here, if applicable.
quarkus.lambda.handler=test
quarkus.package.uber-jar=true
quarkus.native.additional-build-args =-H:-AllowVMInspection
Screenshots
(If applicable, add screenshots to help explain your problem.)

Environment (please complete the following information):
uname -a or ver: Linux localhost.localdomain 5.4.10-200.fc31.x86_64 #1 SMP Thu Jan 9 19:58:12 UTC 2020 x86_64 x86_64 x86_64 GNU/Linujava -version: openjdk version "11.0.6" 2020-01-14mvnw --version or gradlew --version):Additional context
Some indications can be found here :
https://qiita.com/kencharos/items/69e43965515f368bc4a3
https://github.com/oracle/graal/issues/841
https://github.com/kencharos/try-graal-lambda
https://github.com/kencharos/graal-native-on-lambda
/cc @patriot1burke
--environment Variables={DISABLE_SIGNAL_HANDLERS=true}
@gsmet The docs used to go over the function creation scripts and important flags passed, but, against my wishes the current version of the docs removed this. I guess I have to go update the docs to describe the important flags to pass again.
This documentation : https://quarkus.io/guides/amazon-lambda shoud be update according to that documentation : https://quarkus.io/guides/amazon-lambda-http
With :
Finally, there鈥檚 an environment variable that must be set for native GraalVM deployments. If you look at sam.native.yaml you鈥檒l see this:
Environment:
Variables:
DISABLE_SIGNAL_HANDLERS: true
This environment variable resolves some incompatibilities between Quarkus and the Amazon Lambda Custom Runtime environment.
@geniusit See above, there's a command line switch you can pass when you create the lambda:
--environment Variables={DISABLE_SIGNAL_HANDLERS=true}
@geniusit See above, there's a command line switch you can pass when you create the lambda:
--environment Variables={DISABLE_SIGNAL_HANDLERS=true}
Yes, it works with that env variable. Thank you!