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.
Hello,
Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.
Unfortunately, DigitalOcean Spaces does not currently support setting a default ACL for new objects. As a workaround, when you upload new files to your Space, you must specifically set the ACL to public-read for each file. You can do this using the following command:
aws s3api --endpoint=https://<REGION>.digitaloceanspaces.com put-object-acl --acl public-read --bucket <YOUR-BUCKET-NAME> --key <YOUR-FILE-NAME>
Alternatively, you can use the s3cmd tool:
s3cmd setacl s3://<YOUR-BUCKET-NAME>/<YOUR-FILE-NAME> --acl-public
For more information on working with DigitalOcean Spaces and ACLs, please refer to the DigitalOcean documentation.
Hope that this helps!