willnorris / willnorris/imageproxy
Question on minio backend
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 513
- PR merge metrics
- No merged PRs in 30d
Description
Hello dear will
I'm using your image proxy on top of minio, and it is really awesome.
but I have a problem on setting ACCESS_KEY_ID and SECRET_KEY of minio.
I want to remove any policies from minio bucket and only let accessing images to whoever that has
correct access key. but when I remove read only from my minio bucket and I set AWS_ACCESS_KEY_ID and AWS_SECRET_KEY
in variables of imageproxy compose file, I can not access images using proxy anymore and I have to add readonly into bucket
policies and then everyone can see images even outside of proxy. is there a way to let imageproxy connect to minio using
access key?
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 with the imageproxy compose configuration and the AWS_ACCESS_KEY_ID and AWS_SECRET_KEY environment variables, then reproduce the request against a Minio bucket without a read-only policy. Trace how the proxy authenticates to the bucket and verify that images remain inaccessible directly while authenticated proxy requests succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100