+1

+1 this is stopping me from using spaces, I’m having to use S3 instead.

+1 this is clearly a deal breaker

Thanks for the feedback. This is something we are looking at. The limitation is unfortunately on the key-based permission support on the Ceph side but we are looking at other ways to mitigate this problem.

Totally dead breaker not having this for sooo many ppl, myself included.

Please, please, please DO, we beg you, prioritize this pleaaasee!!!

There is a feature request where ppl can vote:
https://ideas.digitalocean.com/ideas/DO-I-320

I agree - this needs to be a thing.

Very important! +1

wow, almost 2 years old issue and this still hasn’t been added?

+1 otherwise we need a whole other account just for testing. Way too dangerous having dev access to production data while testing.

+1

Spaces should not be advertised as production-ready when it is missing a VITAL SECURITY feature.

Making such an idiotic decision to omit this makes me question the security of other DigitalOcean products now.

This is a huge security hole.

wow, almost 2 years old issue and this still hasn’t been added?

otherwise we need a whole other account just for testing. Way too dangerous having dev access to production data while testing.

Spaces should not be advertised as production-ready when it is missing a VITAL SECURITY feature.

I am in shock. Can echo pretty much every comment above. This seems extremely dangerous for somebody with a dev access key to be able to fully access ANY bucket whatsoever on the account. Why not allow an access key to only access ONE bucket?