Is it possible to scope a Spaces Secret Key to bucket?

I would like to move data from my MinIO as it’s not cheap to host myself as most of the content I’m hosing are non-profit. It’s like 20 applications that can use ObjectStorage backend, and I would be happy to move to Spaces, but I rather not give access key to an application to access ALL data in ALL buckets. If ApplicationA is compromised (they are running in containers), they should access only data managed by ApplicationA and nothing else.

So the question (as the title says), is it possible to achieve this, for example through API calls, or a hidden “experimental” option? If not, do we know any information if it’s coming soon or not?

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Answer from support:

Thanks for reaching out to us. I understand that you are trying to restrict access to your Spaces. Unfortunately, we don’t offer this functionality. With our access keys, you could access any Space on the account with full read write permissions. However, if you created Spaces on different accounts, then they would have separate access keys, but you would have to pay $5 subscription for each account that has Spaces.

Bobby Iliev
Site Moderator
Site Moderator badge
February 1, 2024

Hi there,

A quick update here, custom scopes for DigitalOcean API Tokens is now in beta!

This API token enhancement provides additional flexibility in protecting your cloud resources by letting you select only the necessary scopes.

Please fill out this form if you are interested in participating in the beta..

Custom scopes introduce more specific permissions, like creating Droplets or updating cloud firewalls. Using custom scopes lets you secure your workflows by granting only the permissions the token needs and restricting access to other resources and actions.

Generally, the CRUD scopes map to equivalent actions on the associated kind of resource:

  • Create scope lets you create the resource type and perform additive actions within that resource type. For example, database:create lets you create database clusters and create new users or databases within that cluster.

  • Read scope lets you view information about a resource by type and also view information that the resource returns. For example, app:read lets you view App Platform apps and their logs.

  • Update scope allows you modify a resource type and perform actions that would otherwise modify a resource. For example, droplet:update lets you power a Droplet on or off.

  • Delete scope lets you delete a resource by type and perform actions that delete information about the resource type. For example, database:delete lets you delete databases from a database cluster and remove existing users from a database.

Each custom scope correlates to one public API endpoint.



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel