neo4j/neo4j-ogm-quarkus

SSL connection issues when running in native mode on AWS Lambda

sennetheunisporphy opened this issue · 1 comments

Hello

I'm using this driver to connect to Neptune on AWS when running in a lambda.
I used the AL2_PROVIDED runtime. When I deploy it to the lambda, it always throws this:

2022-09-27 15:28:58,918 ERROR [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread (NORMAL)) Failed to run lambda (NORMAL): org.neo4j.driver.exceptions.ServiceUnavailableException: Connection to the database terminated. Please ensure that your database is listening on the correct host and port and that you have compatible encryption settings both on Neo4j server and driver. Note that the default encryption setting has changed in Neo4j 4.0.

If I run this locally, I can connect just fine to the Neptune DB. When I deploy it in JVM mode to lambda it also works.
Any ideas of what could be wrong?

I just the bolt driver and configure it uses the appsettings:

quarkus.neo4j.uri=bolt://xxx.eu-central-1.neptune.amazonaws.com:8182 quarkus.neo4j.encrypted=true quarkus.neo4j.authentication.disabled=true

Using jdk 11 as target version btw.

Sorry I needed to compile using ./mvnw clean package -Dnative -Dquarkus.native.container-build=true