Connecting to Neptune over Secure Websocket wss://

[jinman]

This is a great visualizer. We are trying to connect to Neptune over secure websocket. we changed the proxy-server.js to connect to wss:// instead of ws://. However, its still unable to connect and does not give any errors as well. Has anyone been able to connect this library to Neptune securely over SSH tunnel recently (after they mandated HTTPS/SSL/WSS)? Please help.

[Givemeurcookies]

Works for me. Remember that Neptune requires servers to be connected via VPC. The proxy server has to be i.e on an EC2 with the same VPC as your Neptune database.

[yaaraze]

@jinman We found a workaround, in line 59 in proxy-server.js we also do:

const client = new gremlin.driver.Client(`wss://${gremlinHost}:${gremlinPort}/gremlin`, { traversalSource: 'g', mimeType: 'application/json', rejectUnauthorized: false });

[jinman]

@yaaraze were you able to connect without the SSH tunnelling?

We are only able to connect to via SSH tunnel

SSH tunnel

ssh -i .pem ec2-user@ -L8182::8182 Set chrome://flags/#allow-insecure-localhost

[tomdistler-automox]

@prabushitha I don't have permission to open a PR, so here's the change I'd suggest to support multiple protocols (a secure connection is required by AWS Neptune)

proxy-server.js:59

const client = new gremlin.driver.Client(`${process.env.GREMLIN_PROTO || 'ws'}://${gremlinHost}:${gremlinPort}/gremlin`, { traversalSource: 'g', mimeType: 'application/json' });

Then update README.md to also show: GREMLIN_PROTO=wss npm start