aws / amazon-neptune-sigv4-signer

A library for Amazon Neptune that enables AWS Signature Version 4 signing for HTTP using Netty.

Amazon Neptune SigV4 Signer

A library for sending AWS Signature Version 4 signed requests over HTTP to Amazon Neptune. This package provides signers that can be used with various implementations of HttpRequests:

1. NeptuneApacheHttpSigV4Signer.java - provides an implementation for signing Apache Http Requests.
2. NeptuneNettyHttpSigV4Signer.java - provides an implementation for signing Netty Http requests
3. NeptuneRequestMetadataSigV4Signer.java - provides an implementation for a generic Request object RequestMetadata. A user of this class can convert their native HttpRequest into a RequestMetadata object and pass it to this class to create the signature.

For examples of usage of this library refer to:

1. Connecting to Neptune Using Java and Gremlin with Signature Version 4 Signing
2. amazon-neptune-sparql-java-sigv4 - Contains examples for sending SigV4 signed requests with Apache HttpUriRequest objects.

For more documentation around IAM database authentication for Neptune refer to Identity and Access Management in Amazon Neptune

For the official Amazon Neptune page refer to: https://aws.amazon.com/neptune

License

This library is licensed under the Apache 2.0 License.

amazon-neptune-sigv4-signer's Issues

Add java.net.http.HttpClientHttpSigV4Signer

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/

Facing 403 Forbidden when SigV4 is used

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?

Upgrade to use AWS Java SDK v2

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.

Release of new version

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