Access denied for new file uploaded to Spaces when accessing via custom Subdomain and Edge URL

I ran into this issue too, I found a solution for me. I have Laravel Media Library from Spatie uploading media for me using my DO Space. I had to add a new header to media-library config under remote.extra_headers. The line I added was 'ACL' => 'public-read', and that will add the needed header/argument that DO uses to determine if the file should be public or not.

Hope this helps.

I also get a 403 access denied

user@app-w-1:~/domain.com/current/storage/logs$ tail -n 70 laravel.log
[previous exception] [object] (GuzzleHttp\\Exception\\ClientException(code: 403): Client error: `PUT https://app-stuff.ams3.cdn.digitaloceanspaces.com/assets/logo.domain.com/js/site.js` resulted in a `403 Forbidden` response:
<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error><Code>SignatureDoesNotMatch</Code><RequestId>tx0000000000000198831c1-005ef2 (truncated...)
 at /home/forge/domain.com/releases/145/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113)
[stacktrace]

Origin does work. Looking into way to put using origin and load using EDGE.

How is this not getting much attention? This seems to be a big issue that basically makes DO Space useless