Storage

Dear DigitalOcean Team, In line with our efforts to establish a reliable and scalable infrastructure for our university's academic and research initiatives, we are pleased to share with you our official Service Level Agreement (SLA) document. This document outlines the infrastructure requirements, service expectations, and operational standards that form the foundation of our collaboration goals. We believe DigitalOcean’s robust platform could be a strong match for our needs. 📄 We invite you to review the attached SLA and share any feedback or questions you may have. Your insights would be invaluable in helping us shape a reliable and future-proof solution. You can download the SLA document here: https://1drv.ms/u/c/4bdcd901932daa1e/EdSQnxXr3-ZNsU9WrxdZqVoBunH1zWFXuRk4QqfnEEMkrQ?e=Coj9p0 Should you be interested in discussing this further, we would be happy to arrange a call or meeting at your convenience. Thank you for your time and consideration. Best regards, Dounia Khoury

With yesterday's outage of Spaces of over 4 hours, why is there no SLA for Spaces availability? This was a costly outage but customers have no recourse. There's no mention of Spaces SLA here: https://docs.digitalocean.com/platform/slas/ . Can DigitalOcean consider adding one to protect against future incidents? Consider competitor SLAs: Amazon S3: https://aws.amazon.com/s3/sla/ Backblaze B2: https://www.backblaze.com/company/policy/sla

Please prioritise having individual keys for individual spaces. It's pretty useless with multiple products or clients. I can't use it for backup for instance, because every other project will be able to access these backups if compromised.

Currently there is the option for spaces access keys to either be fullaccess or read/write/delete scoped on one or several buckets. An access key which has read on a bucket still can't do something like "s3cmd info s3://<bucket-name>". Ideally there is something like a fullread key that allows reading all the information in Spaces.

I've got Spaces buckets configured via CDN. When a user goes to the CDN hostname of the bucket without any real file request it will get a general access denied response. But that response reveals the bucket name. That can be a security risk as it sometime ties into application names or references to other hostnames you're using in the system. No reason to reveal that info to someone requesting the main url for no legit reason. The bucket name should not be included in the access denied response or it should be a config setting you can disable/enable.

It would be nice to be able to access metrics such as storage consumption and bandwidth via the Monitoring API.

S3 Object Lock's Governance Mode allows you to protect objects from accidental deletion or modification by most users, but it allows users with specific permissions (like s3:BypassGovernanceRetention) to override these protections. This mode is useful for scenarios where you want to experiment with object locking or need a way for administrators to manage retention settings while still preventing accidental changes by regular users. With out lock functions in Spaces, Digital Ocean is not a solid contender for big companies that need Governance Mode Backups stored in S3 Buckets, can be deleted by the ramsonware attacker or by a sabotage employee. Please consider add this function to Spaces Thank

It would be amazing being able to optimize and transform images on the go using the CDN, that would be an even bigger plus on using DigitalOcean's CDN to host images, it will make website optimization a lot easier. Example: https://web.dev/image-cdns/

Object storage pre signed URL limit number of downloads, that features is missing please add this useful feature.