Question
Is it possible to mount DO Spaces as external storage in Nextcloud as I mount AWS S3 storage?
- Posted October 11, 2017
- Object Storage
I’m using $5 Droplet for my Nextcloud instance. It is possible to mount AWS S3 buckets in Nextcloud as an external storage. So is it possible to mount Spaces as S3?
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.
Yes! Spaces was designed to be compatible with S3 in order to take advantage of existing integration just like this. In order to mount a Space for external storage, you first need to enable the External Storage Support plugin just as you would for S3.
Next, add a new mount from the External Storages menu in the Admin panel. In the Bucket field, add the name of your Space. In the Host field, enter nyc3.digitaloceanspaces.com. In the Region field, use nyc3. You can fine the needed Access Key and Secret Key for your Spaces account on the Applications & API page of the DigitalOcean control panel. Finally, make sure to select Enable SSL. When successfully configured, a green dot should appear:
Additionally, you might want to enable sharing. This can be done the the Advanced Settings which can be accessed by click the “cog” icon on the right:
Is it possible to add only a folder in a space? I have my space set as primary storage but I’d like to have more granular control over who sees what folders. If I could add folders individually, I could set group access rights to each folder.
Unfortunately NextCloud’s group folders app only works at the root level so any folders I make in it don’t show up at all if i’m using a space for primary.
I love this setup so far, I just don’t want to have to pay for a new space just to give each person a private folder!
@asb Unfortunately, this solution is not working for me. I configured a space first (bucketname e.g. bucket1), but NextCloud is trying to PUT a bucket of that name for storage. The bucket name already exists, so the configuration fails. “Creation of bucket ‘bucket1’ failed. Error executing Create Bucket on https://bucket1.sfo2.digitaloceanspaces.com. 409 Conflict Bucket Already Exists.” From what I can tell, the S3 configuration in NextCloud is expecting to be able to create buckets, but when you use a space, the space itself is already a Bucket, so NextCloud is unable to create it. If you put a Space that doesn’t exist as the bucket name, it gives a 403 permission denied, because you can’t create buckets in spaces through the API, or at least not through how NextCloud is trying to do it.
For Folder Name I’ve tried “/” and “AmazonS3.” Bucket is ‘bucket1’. Hostname is sfo2.digitaloceanspaces.com. Port is left empty. Region is sfo2. Enable SSL is selected. Not sure what else to try. If that doesn’t work I probably can’t use Spaces for this, which I’d like to.
I cannot get this to work. I’ve followed the DO tutorial for installing Nextcloud on Ubuntu 16.04 and now this one…no matter what, I always get a big red square.
I’ve seen some posts about Spaces not being compatible with NextCloud 13 (https://github.com/nextcloud/server/issues/7789). Wondering if anyone else has this working with the latest version of NC.
This comment has been deleted
Great answer! Thanks for share!