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.

This is terrifying! Imagine if one of your API keys were to become compromised. They would have access to all of the data within all of your spaces. I can't imagine a more serious security threat to DO's infrastructure than this. Especially since this exploit is known to the public now. In fact, the more I think about it, why even give users the ability to add different API keys?

Seriously!?

At least we should be able to separate access keys by projects like the spaces are separated.

This is pretty embarrassing this feature is missing. Ability to segregate buckets into different security boundaries is so important.

I am shocked that this is missing. Obviously making some of my use cases insecure for my customers.

Disapointing.

I still can't wrap my head around this. DO, what are you thinking?! Unfortunately, I just wasted 5 bucks. I really really wanted to use this for customer backups, but there's no way.