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

Question

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?

Bobby Iliev · Accepted Answer

Hi there! 👋

Quick update: DigitalOcean has implemented the ability to have different access keys per bucket in Spaces!

This allows you to limit access to specific buckets with unique keys and secrets, giving you more control over who can access your data.

For full details, check out the official documentation here: 🔗 Manage Access Keys for Spaces

A couple of things to note:

Legacy “All Permissions” access keys cannot be converted into per-bucket keys — you’ll need to create new ones.
Currently, access keys can only be created in the UI (API support is on the way!).
Buckets using PutBucketPolicy support only legacy keys for now, but integration with per-bucket keys is in the works.

DigitalOcean will be be announcing the feature to the wider community soon!

- Bobby

Victroia Nadasdi · Answer

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 · Answer

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.

Best,

Bobby

Question

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

Become a contributor for community

DigitalOcean Documentation

Resources for startups and SMBs

Get our newsletter

The developer cloud

Get started for free