Sébastien Crocquesel

Looking into the aforementioned issue, it is related to another SDK that this extension is primarily focused on ([`aws-sdk-java-v2`](https://github.com/aws/aws-sdk-java-v2)). There is another [issue](https://github.com/quarkiverse/quarkus-amazon-services/issues/1201) requesting an AWS JDBC driver extension. Given...

@gastaldi @gsmet any thoughts on my previous comment ?

The root cause has been fixed in the upstream repo by upgrading to AWS SDK v2. I'm closing this issue but if the problem persist with the v2, open a...

Could you provide a bit more details on the error and the proxy's required authentication type (basic, ntlm) ? Maybe you can have more details on the 407 returned by...

@radcortez Is is expected that we cannot share the root prefix in two different packages ? Is it because in we use interface mapping in the extension while quarkus is...

It seems there are limited solutions available: - Alter the configuration prefix to "lambdaclient." However, this adjustment would deviate from the convention used for all other extensions, where the artifact...

I'm a bit busy atm @emakunin would you mind provide a repro plz

@emakunin @GheorgheGanea Version `3.0.0.alpha1` is out. Could you have a look at it.

> I have the need to write a lambda to invoke another lambda, so I though that using the `io.quarkiverse.amazonservices:quarkus-amazon-services` LambdaClient would be the correct approach. > > On 2.8.1...

I believe this falls somewhat outside the scope of this project, which primarily focuses on providing support for the [AWS SDK](https://github.com/aws/aws-sdk-java-v2). I guess the JDBC driver deserves a new Quarkiverse...