Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] URL scheme is ignored when sign_aws_requests is enabled #223

Open
riconnon opened this issue Nov 20, 2024 · 1 comment
Open

[BUG] URL scheme is ignored when sign_aws_requests is enabled #223

riconnon opened this issue Nov 20, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@riconnon
Copy link

What is the bug?

When sign_aws_requests is set the scheme from the url parameter is ignored and it always attempts to connect via HTTPS

How can one reproduce the bug?

  1. Set URL to http://127.0.0.1:8080 or similar
  2. Set sign_aws_requests to true
  3. Make some requests

What is the expected behavior?

The requests are made via HTTP to the local address with AWS signature in the Authorization header

What is your host/environment?

macOS 15.1.1

Do you have any screenshots?

N/A

Do you have any additional context?

I'm using quite a peculiar setup which warrants this configuration.

I have a reverse proxy in front of my OpenSearch domain which listens for mTLS connections and forwards the requests to AWS OpenSearch.
For this I need to do AWS signing on my requests but also wrap that with mTLS to our custom endpoint.
Since our client certificates are typically stored in macOS keychain we can't configure this using client_cert_path and client_key_path so I was going to use a separate local signing proxy to do the signing which I have bound to a HTTP listener on a loopback address.

@bshien
Copy link

bshien commented Nov 21, 2024

[Triage] Can you confirm if everything is ok with reverse proxy? See: #215 (comment) @rblcoder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 📦 Backlog
Development

No branches or pull requests

3 participants