Upload to cloud (s3 bucket scaleway) files permission denied

[AbM7797]

I'm facing a problem when uploading the shaka auto-generated files to the cloud (s3 bucket scaleway), all the files are private and I didn't find any configuration to change the visibility of the files from private to public.
Is there a custom boto configuration?
This is my configuration:

[Credentials]
aws_access_key_id=xxxxxxxxxxxxxxxxxxxxxxxxx
aws_secret_access_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
s3_host=xxxxxxxxxxxxxx
region_name=fr-par
endpoint_url=http://xxxxxxxxxxx
service_name=s3
use_ssl=True
acl_public=True
acl=public-read

[s3]
calling_format = boto.s3.connection.OrdinaryCallingFormat
acl=public-read
acl_public=True

[joeyparrish]

I don't know how to do it for S3, but I know how to do it for GCS. It has to do with access controls on the bucket. In GCS, if the bucket is set to allow read-only access from allUsers, then anyone can read the files without authentication. There must be a similar thing in S3, but you'll need to search the S3 docs for that.

Does this help?

[github-actions]

@AbM7797 Does this answer all your questions? If so, would you please close the issue?

[AbM7797]

@joeyparrish My bucket is already public but when shaka uploads the files it sets them to private.

[joeyparrish]

Upload today uses the external command gsutil cp (though we are working to change that in PR #103). Since we're only using gsutil cp, try copying a file into your bucket with that command. If that file is also not public-readable, I strongly advise you to look into your bucket settings. We don't directly set anything related to access control.

[github-actions]

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.