Is there an existing issue for this?
What are you currently unable to do
Since access keys for s3 buckets can only be created per bucket within incus, this poses a challenge when working with applications that need to access multiple buckets but expect to be able to work with a single access key (a ubiquitous pattern for s3 storage). This could be worked around by using the same access key and secret key for multiple buckets, but incus does not allow this at the moment.
What do you think would need to be added
Imo, there are two ways to solve this:
-
Quick and somewhat dirty: Remove the constraint preventing to create access keys with the same id for different buckets. That way, while technically separate keys are used to access the buckets, an application could be convinced it's the same key.
-
Allow the creation of access keys outside of the scope of a single bucket (or expressed differently: allow defining roles for multiple buckets for an access key).
Is there an existing issue for this?
What are you currently unable to do
Since access keys for s3 buckets can only be created per bucket within incus, this poses a challenge when working with applications that need to access multiple buckets but expect to be able to work with a single access key (a ubiquitous pattern for s3 storage). This could be worked around by using the same access key and secret key for multiple buckets, but incus does not allow this at the moment.
What do you think would need to be added
Imo, there are two ways to solve this:
Quick and somewhat dirty: Remove the constraint preventing to create access keys with the same id for different buckets. That way, while technically separate keys are used to access the buckets, an application could be convinced it's the same key.
Allow the creation of access keys outside of the scope of a single bucket (or expressed differently: allow defining roles for multiple buckets for an access key).