Share your feedback...
Granular API token access to Object Storage (Spaces)
DigitalOcean does not yet have granular API token access as an option. As the API tokens are now give access to all Spaces on the same account which is not optimal for us as a web agency. We could create an account for each client, but this will give us hundreds of accounts and much more extra work for our bookkeeper.
Necessidade de implementar no banco de dados postgresql as
pldbgapi e quantile extension for postgresql
Object Storage in London
I need my data to remain in the UK at rest but Spaces is not available in LON1
Default to index.html in Spaces
Navigating with a browser to a spaces bucket yields a terrible looking giant XML file. What I'd like is to be able to host an index.html file in the space, and have navigation to / default to /index.html. This idea has been discussed for years , and while it was claimed to be worked on, it was never completed. This is a hugely important feature for a lot of people.  https://www.digitalocean.com/community/questions/spaces-set-index-html-as-default-landing-page
Spaces in tor1
Since the 2 ideas of spaces in TOR1 was closed 2 months ago without any explanation ( https://ideas.digitalocean.com/storage/p/spaces-on-tor1 and https://ideas.digitalocean.com/storage/p/spaces-for-tor-region ) I'm gonna have to recreate a new idea about it.
Signed URL on Spaces CDN
While using CDN with Spaces, allow the possibility of creating signed URL for CDN endpoints. Currently, if we set the CDN on a private bucket, the content can be accessed from the CDN endpoint by knowing the filename.
Access key per space
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.