qdrant / qdrant/qdrant

Support to use IAM role when uploading snapshots to S3

Open
#4,749 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triage
Dominant language
Rust
Stars
34.7k
Forks
2.7k
Avg merge
1d 18h
Merged PRs (30d)
187

Description

Is your feature request related to a problem? Please describe.
Support to use IAM role when uploading snapshots to S3. We deployed our Qdrant cluster in EKS, so it's more reasonable to use iam role to upload snapshots to S3.

Describe the solution you'd like
When s3_config is configured, but access_key/secret_key are not set in configuration file, then it should use iam role which specified in service account to upload snapshots to S3.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by tracing the snapshot upload path and the s3_config handling, then determine how access_key and secret_key are selected when absent; done means uploads work through the IAM role specified by the EKS service account without static credentials.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, rust
Domain
backend, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.