Yeah it's the last dangling string left for s3 about to move everything back.

Completely blows my mind that this wasn't implemented in the first place and even more so that it's not implemented now after all this time. Pretty much makes DO Spaces useless which is very unfortunate and even more unfortunate that DO doesn't seem to care about such a gaping hole in their security.

Has this not been sorted yet?

This is the only thing that is keeping me using S3 instead of Spaces. Basic security with obvious solution. Come on DigitalOcean

Not evening talking about RBAC, simple assignment of keys per project or per resource such as space would be good enough. As of today the only way to have a production grade secured environment is to have a seperate user account for each application/environment pair such as app1/staging app1/production app2/staging app2/production. Please do something about it. Does anybody at DO have basic security knowledge ?

Very important. I need to segregate access to spaces per key, as well as basic other rights such as having "read-only" or "write-only" keys.

This is the one missing feature making me regret choosing DigitalOcean and making me strongly consider moving all of our infrastructure to one of the bigger cloud providers.

I agree, this would be super-useful!

We need the ability to create keys per space and limit the access to that key in the event of a breach, i.e IP restrict and/or VPC control. Similar to managed databases.

CORS settings help to a degree by limiting which origins may access a space, but more granular controls are needed for allowing bearers of specific API keys to access specific Spaces.