+1 An upload into a directory that has public ACL does not inherit such settings.

I got the same issue. How to automatically set new uploaded files as PUBLIC?

This might help everyone. I just solved the issue when uploaded file to space, by default is set to private. This is how you can change it to public. Full code, btw this is node:

const 
  s3 = require('s3'),
  GV = require('/path/to/config/file');

let client = s3.createClient({
    s3Options: {
      accessKeyId: GV.digitalOcean.spaces.key,
      secretAccessKey: GV.digitalOcean.spaces.secret,
      region: GV.digitalOcean.spaces.region,
      endpoint: GV.digitalOcean.spaces.endpoint
    },
  });

let 
        params = {
          localDir: '/local/path/file',
          deleteRemoved: true,

          s3Params: {
            Bucket: GV.digitalOcean.spaces.bucketName,
            Prefix: '/remote/path/file',
            ACL: 'public-read'  // this should set the file to Public
          },
        },
        uploader = client.uploadDir(params);

      uploader.on('error', function(err) {
        console.error("unable to sync:", err.stack);
      });

      uploader.on('progress', function() {
        console.log("progress", uploader.progressAmount, uploader.progressTotal);
      });

      uploader.on('end', function() {
        console.log('done');
      });

Not being able to set the default permissions in a space is a big problem. I don’t think that the code snippets shared above are a real solution.

Collaborators on my projects should be able update content in the space, without running any code. It seems like the real fix would be for DigitalOcean to implement decent permissions inheritance.

It turns out DO buckets are fully compatible with S3, down to the bucket policy level. I was able to follow this guide: https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteAccessPermissionsReqd.html

Specifically, setting the bucket policy to allow public access worked. Here is the command I used with the AWS CLI:

aws --endpoint-url=https://nyc3.digitaloceanspaces.com s3api put-bucket-policy --bucket=<BUCKET> --policy file://policy.json

policy.json

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject"
            ],
            "Resource": [
                "arn:aws:s3:::<BUCKET>/*"
            ]
        }
    ]
}

Hello friend!

This can definitely be done. I have some documentation here that can help:
https://www.digitalocean.com/docs/spaces/how-to/file-permissions/

Kind Regards,
Jarland

HI, the only way to edit multiple files permissions is to go into a folder, select all and then select ACTION dropdown, it allows you to edit permission for all selected files. However this does NOT work when you select all (select all files in this folder).

I think this needs to be fixed because it cost me time and time is money

s3.putBucketPolicy({
    Bucket: process.env.BUCKET,
    Policy: JSON.stringify({
        "Version":"2012-10-17",
        "Statement":[
            {
                "Sid":"PublicRead",
                "Effect":"Allow",
                "Principal": "*",
                "Action":["s3:GetObject","s3:GetObjectVersion"],
                "Resource":[`arn:aws:s3:::${process.env.BUCKET}/*`]
            }
        ]
    })
}, (err, data) => {
    if(err) {
        console.log(err)
    } else {
        console.log(data)
    }
});

With the aws-sdk you can update the bucket policy so all files will get this when uploaded. I still can’t get it to work for the edge CDN though.

correction it does work, you select ALL, then scroll down so more files load, then select all again. You should now be able to change permissions. Still it would be nice to have some more functionality on file and folder management, its basic at best but does the job I guess