S3 Resource Upload not setting ACL

💬 App Building
1
  1. My goal:
    Upload file to S3 that is public-read
  2. Issue:
    Uploaded files are created but have no ACL
  3. Steps I've taken to troubleshoot:
    I've tested the query from the resource editor, created a new app from scratch, and get different results.
  4. Additional info: (Cloud or Self-hosted, Screenshots)
    Cloud

I've set the default ACL on the resouce to "public-read"
I use the "Test Query" button and in the test it will successfully upload the file and save the ACL.

However, it doesn't work from any app. I tried in an existing app with no luck. I tried creating a new app, and a new Resource Query, all from scratch, and consistently it will upload the file, but not apply the URL.

The difference is clear in the signedUrl response from the query. In the Test Query, it shows x-amz-acl=public-read as part of the URL, but this is not present in the signedUrl returned when used from an app.

I've used the S3 Uploader control many times over the years, but now that it is deprecated I'm finding the S3 Resource to be fatally flawed.

Could the apps be somehow picking up an older version of the resource? If so, how can I get it to pick up the new one? I'd create a new resource but that would require new credentials from AWS and getting our other departments involved.

2

I have to add, preference would be not to make the DEFAULT ACL "public-read", but using the resource queries does not appear to provide an alternative. Using the S3 Uploader, we could override, so the "Default" really was just a default, but using the resource from a resource query, we have no ability to set this. Seems like a big oversight.

3

Alright...issue turned out to be simple, but highlights why ability to set the ACL on the resource query would be much better.

We have 4 environments. I only set the default ACL on the production environment. Have to go through each environment one by one and set something like this for each one of them.

Please please...provide the ACL option on the resource query!!