By hashibuto
A major limitation of Spaces right now, is the inability to isolate one bucket from another via Spaces API token. Granted this is not a full S3 implementation, it would be very beneficial to be able to create multiple buckets and associate an access key with each.
My question is, are there plans in the near future to add more granular access control? Right now it’s all or nothing which is fine for many scenarios, however when there are different areas of trust, it would be nice to be able to store certain data in one bucket and other data in another, whilst granting access to each via separate tokens (circles of trust).
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there @hashibuto,
At this time there are limitations to our Spaces Access Keys. There is a community suggested idea that you can show your support on asking for more robust access keys. This is something our product team is evaluating so additional feedback there won’t hurt!
With regards to a workaround in the meantime, using Team Accounts with separate Access Keys + Spaces will help divide up your Spaces/Access Keys into usable groups.
Hope that helps! - Matt.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.