UI for Neptune Analytics does not honor proxy configuration

[jicowan]

Description

1. UI saved the connection, but when the app made requests, it used the Neptune URL directly (https://g-mdpui2k10a...) instead of routing through the proxy (https://localhost/...)
2. The proxy toggle wasn't being respected - even though I enabled it in the UI, the frontend code path for Neptune Analytics connections appeared to bypass it
3. defaultConnection.json worked because it's loaded at startup and the app treats it as a trusted/pre-configured connection, possibly using a different code path that correctly respects the proxy setting

Environment

Running local Docker container which is mounting my /.aws directory

• OS: MacOS
• Browser: Chrome
• Graph Explorer Version: v3
• Graph Database & Version: Neptune Analytics

Steps to Reproduce

1. Configure Neptune Analytics connection via UI with proxy enabled
2. Requests go directly to Neptune instead of through proxy
3. Workaround: pre-configure via defaultConnection.json

Expected Behavior

I expect it to honor the settings configured in the UI.

---

Important

If you are interested in working on this issue, please leave a comment.

Tip

Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.

[kmcginnes]

@jicowan Thanks for the submission. Would you mind showing a screenshot of the edit connection modal? Be sure to blur anything sensitive before posting.

[jicowan]

i set the proxy to https://localhost and configured the region to match where I've deployed neptune analytics. the graph type is openCypher.

[kmcginnes]

@jicowan Does your connection look something like this?

[jicowan]

That's looks about right.

[kmcginnes]

@jicowan In case you were not aware, Neptune Analytics supports using public endpoints, which would remove the need to use SSH tunnels entirely. However, I understand that is not always possible.

If your SSH tunnel setup is anything like mine, it would require modifying your /etc/hosts file.

127.0.0.1       <cluster-or-graph-endpoint>

[kmcginnes]

@jicowan I'm going to go ahead and close this. If the issue is still persisting, then please re-open it with any new details.