Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
According to support, granting READ permission to AllUsers on a bucket just means they can list the bucket contents…
I don’t understand why there is not a ‘read any object’ permission on a bucket or a directory inside a bucket? Can anyone enlighten me? Seems like such a common use case.
Thanks!
Well, I answered a couple of my own questions, but it’s still not working.
I figured out that by using the Java API, or any other API it’s a lot easier to get and set the ACL. I am now able to do that, so I got my owner ID.
My current ACL looks like this in Java:
AccessControlList [owner=S3Owner [name=MY-OWNER-ID,id=MY-OWNER-ID], grants=[Grant [grantee=GroupGrantee [http://acs.amazonaws.com/groups/global/AllUsers], permission=READ], Grant [grantee=com.amazonaws.services.s3.model.CanonicalGrantee@e3da3b58, permission=FULL_CONTROL]]]
I granted myself full access and “AllUsers” read. However when I upload a new file using either the java api or s3cmd, it still is not readable in the browser :(
Any ideas on why it is not working? Thanks again!
Using the following command I can mount a bucket on AMAZON_S3 so that any file placed there is then publicly accessible. I copy any file in
s3fs fcdn /var/www/fcdn -ourl=https://s3.us-east-2.amazonaws.com -o default_acl=public -ononempty
All subsequent copies to /var/www/fcdn immeditely appear on AMAZON_S3 and are always publicly readable. No issues.
However, when I mount to DO_Spaces with s3fs fcn /var/www/fivecent/image -ourl=https://nyc3.digitaloceanspaces.com -o default_acl=public
A subsequent copy of a file to image folder or per say to fcdn folder simply fails with cp zimage/*.png image/ cp: cannot create regular file ‘image/no_image.png’: Input/output error cp: cannot create regular file ‘image/placeholder.png’: Input/output error
Apparently there is a bug in the S3 API at DO. Hope someone looks into it.
Regards.