Background:
The Storj web dashboard currently allows customers to specify storage and download limits for a project.
With Storj offering multiple storage classes (Global, Regional, and Active Archive), being able to set more specific limits would be helpful to prevent unexpected costs, especially for storage classes like Active Archive which have no included egress.
Requests:
- In addition to the current per-project limits, allow storage/download limits to be specified for all buckets of a specific storage class in a project For example, all Global buckets combined in a given project could be limited to 10TB storage and 10TB download per month, all Active Archive buckets combined in a given project could be limited to 5TB storage and 1TB download per month, etc.
- Same as above, but more specific and applied to a given bucket. For example, the bucket “abc” could be limited to 5TB storage while the bucket “xyz” could be limited to 1TB storage and 500GB download.
- Same as above, but for individual linkshare links. A malicious (or misconfigured) system possessing a valid linkshare link could incur significant egress costs for a customer by repeatedly downloading a file. Having more fine-grained control, such as a linkshare link expiring after a certain number of downloads, a certain amount of data transferred, etc. in addition to the current optional expiration date, could reduce the potential for abuse/misuse.
Considerations:
All applicable limits should apply simultaneously, with more-specific limits (e.g. per-bucket) being allowed to be more restrictive than more-general limits (e.g. per project) but not being allowed to be more expansive. The limit-setting UI should make it clear to the user which limit is “controlling” to avoid confusion: “You can’t set the limit for this bucket to 10TB download because the download limit for the overall project is 5TB.”
Thank you.