Storage

Currently, to use a custom domain with DigitalOcean Spaces CDN (e.g., cdn.example.com pointing to my-space.fra1.cdn.digitaloceanspaces.com ), I need to transfer my entire domain's DNS management to DigitalOcean nameservers. This is problematic because: Many users prefer managing DNS with Cloudflare for better performance, DDoS protection, and advanced features Domain consolidation - users want to keep all domains in one DNS provider Current workarounds are complex - requiring Workers, redirects, or proxies that break the user experience Proposed Solution: Allow custom domain verification through: DNS TXT record verification (like most CDN providers) CNAME verification method File-based verification on the domain Benefits: Users can keep their preferred DNS provider Simpler setup process Better user experience with branded CDN URLs Competitive with other CDN providers (Cloudflare, AWS CloudFront, etc.) This would make DigitalOcean Spaces more competitive and user-friendly for developers who want branded CDN URLs without the complexity of full DNS migration.

remove the old images automatically from registry if quota is exceeded

HDS (Hébergeur de Données de Santé) HDS is a compliance thing in France to save medical/health data. If you don't use a cloud provider that has HDS, CNIL (French Regulator) can fine you and ANS will not give you a certification. AWS offers such type of storage. AWS also has the following certificates: ISO/IEC 27001:2022, 27017:2015, 27018:2019, 27701:2019, 22301:2019, 20000-1:2018, 9001:2015 et CSA STAR CCM v4.0. Please look at providing this type of storage to attract Health Tech companies.

I have been using DigitalOcean for many years and am currently working on a big data storing project. We found out that AWS S3 have a class for storing long term files with less energy usage (Glacier) - thus making it far more environmental friendly. We would love if DigitalOcean upgraded their Spaces so it has a similar function to Glacier, making it possible to store files for a long time without wasting energy. Thanks

Hello, I like the idea of the 2 week recovery time but this blocks setup and tear down of test environments quickly impossible. Maybe they need to move to temporary project or still allow other resources to be deleted for a force delete option for terraform users. Kindly Matthew

Please allow us to set a description for Spaces to help Developers get more information about spaces. A description can help developers provides context and information about the intended usage of the space. As of the 6th January 2024, the only information we have is the name of the space. The attached image has an example description I added in.

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

It could be great to be able to get emails when volumes harddrive are nearly full like normal droplet.

Please add snapshot scheduling on volume block storage to regularly make snapshot and to avoid needing to do it manually or to give API access to another system. A retention configuration would also be great to remove old snapshots automatically.

Allow Spaces buckets to be either private or public by default with a simple UI to do so in the control panel.