prepare an bucket_access.yml file with these content:

hellworld:
  access_key: "helloworld2"
  secret_key: "ccccccdcssdddddddddddd"
hellworld2:
  access_key: "hellowo2rld2"
  secret_key: "ccccccdc2ssdddddddddddd"
test3:
  access_key: "helloworld3"
  secret_key: "12345122345"
test4:
  access_key: "hello11world3"
  secret_key: "1234511122345"

then using --properties src/main/resources/s3proxy-fs.conf --enable_bucket_ak_sk --config_path bucket_access.yml
to start s3proxy .

All the change in the yaml file will be watched and take affect.

So... I like this idea. whybeyoung here wants to create basic authentication tied to different buckets on the SAME backend. I was looking for a solution for this and have not yet found anything. I thought of launching multiple s3proxy containers but the issue is the backend credentials i'm using grant access to ALL buckets. Is there currently any way to restrict s3proxy to one bucket on a backend? Like with filesystem there is a basedir. A basedir on the s3 backend (which is actually a bucket) would achieve that.