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.

I've just had to abandon a plan to migrate all my S3 buckets to Spaces because I didn't realise this capability was missing. I'm sure it's difficult to implement but this seems like an absolutely essential feature to me. I'm hosting a slate of client sites on DO Droplets and each needs compartmentalised access to its own Space for media files. Having all access keys able to access all Spaces is completely unworkable. Any update on this would be massively appreciated!

I am surprised that this essential feature is missing. Anybody from DO that will explain the reasoning behind this?

This really should be implemented. Even within one application that has multiple Spaces, I do not want Spaces to share access keys. A compromised access key for e.g. encrypted backups should not be usable to retrieve files from the "customers" spaces, revealing GDPR data... Please increase the priority accordingly!

Kinda rediculous the way space permissions work, or should I say lack there of.

Never the less development seems super slow even for critical stuff like this, I guess AWS it is.

This is a mayor security and privacy issue. One keypair shouldn't have unlimited access to everything. It's just plain stupid, and you know it :).

We need to be able to have isolated buckets for each environment (dev/stage/prod), or have isolated buckets for each customer.

+1

This can also help with a variety of automation workflows, and having scoped keys can help reduce the risk / exposure should the keys get compromised.

For example having a dedicated key (scoped to a space) to uploading release artefacts from GitHub action workflows, another key that's read-only to download those artefacts on droplets etc...

Hope to see improvements in this area to aid such workflows.

Thanks!