Hi all,
Background: Currently, Storj lets one choose the storage class (Global, Regional, Active Archive) on a per-bucket basis, and all files in that bucket inherit that class.
Request: I request that storage class be selectable on a per-file basis through the S3 and native APIs and/or through lifecycle rules.
Additional Context: My backup clients (Arq and restic) assume “hot” storage for metadata, in that metadata files are uploaded, downloaded, and deleted regularly. This incurs minimum-duration and egress costs when using an Active Archive bucket to store backups. The backed-up data itself is static (modulo client-selected trimming of old snapshots and similar operations) and is suitable for Active Archive, but metadata would be better stored in Global or Regional.
Neither client can store metadata in a separate bucket, but both support setting different storage classes for metadata and data (such as storing metadata in, for example, AWS S3 Standard, and bulk data in Glacier). Server-side lifecycle rules could also be applied to stored data to change its class over time (e.g., uploading to Global, then transitioning to Active Archive after a period of time).
Thank you.