aws / amazon-neptune-sigv4-signer Goto Github PK

Hello,
Ever since Apache Jena SPARQL version 4.2.0, the default HttpClient in use has been java.net.http.HttpClient. However, there is currently no implementation of a Signer available for this specific HTTP client. Are there any plans on your end to provide support for it?
Thank you in advance.

See https://jena.apache.org/documentation/sparql-apis/

Hi all,
I recently upgraded my cluster from version 1.1.0.x to 1.3.x.x and am facing issues when bumping my gremlin driver to version 3.6.x.

The main issue is that I'm following what your documentation says, to use a handshake interceptor and use the NeptuneNettyHttpSigV4Signer to sign the request, but it's not working, I've got only 403 from the server, and all the configurations are right as they should.

Before upgrading, the project was using the SigV4WebSocketChannelizer which is not working anymore, and this led me to think that this new NeptuneNettyHttpSigV4Signer does not work with WebSocket requests. Is that correct?

Hi, could you please run a release after the latest merge to master?

The last merge has a fix which is required for our deployment but in the maven repo it is still the version 2.1.1.

Thanks in advance,
Leo

The current version of the Amazon Neptune SigV4 Signer library leverages the AWS Java SDK v1.12.241. We need to upgrade to the latest v2 version of the AWS Java SDK.