s3proxy disambiguates backend stores by different credentials, which means that from the application side typically a new client needs to be created to connect to the different backends. To reduce friction, it would be great to be able to configure s3proxy with multiple backends with the same credentials and specify the buckets associated with them.

The specific use case is Azure, where multiple storage accounts are common, but being able to hide that complexity from the application would simplify access.