quickwit-oss / quickwit-oss/quickwit
Support custom STS endpoint
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Is your feature request related to a problem? Please describe.
MinIO now supports STS client authentication, https://min.io/docs/minio/linux/developers/security-token-service.html
This does not seem to be supported currently by Quickwit due to a lack of support for custom STS endpoints.
Describe the solution you'd like
In order to support this, the rust AWS sdk needs to be configured to use a custom STS endpoint. I could imagine a QW_STS_ENDPOINT env var.
Describe alternatives you've considered
Creating and distributing secret keys and access keys in my cluster is operationally challenging and often requires security tradeoffs.
Additional context
If this is pretty low lift I'm happy to take a crack at it, but I'm new to Rust and this project.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Rust AWS SDK configuration and the existing Quickwit environment-variable handling. Check how a custom STS endpoint can be supplied through QW_STS_ENDPOINT, then verify that MinIO STS client authentication works without distributing cluster access and secret keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100