Describe the bug
I get the The bucket does not allow ACLs error when copying or moving files from one AWS S3 bucket to another. The destination bucket has ACLs disabled but the source does not. I've tried setting Default ACL to various values, including None, but still get the same error. There was work to address this issue in the past, e.g. #13386, which is where I first commented on this.
To Reproduce
Steps to reproduce the behavior:
- Setup one AWS S3 bucket with an Object Ownership of Bucket owner enforced, e.g. called
enforced
- Setup another AWS S3 bucket with an Object Ownership of Bucket owner preferred, e.g. called
preferred
- Copy an object to
preferred and set the ACL to allow public read
- Copy the object from
preferred to enforced
Expected behavior
I would expect Cyberduck to detect that the destination has disabled ACLs and so these should not be set after the file contents have been copied.
Screenshots

Desktop (please complete the following information):
- OS: Windows 11
- Cyberduck Version 8.5.6 (39394)
Log Files
I've added a debug log file, but tried to clean any details that are not necessary to debug this, like secrets and names of items. If there are details missing that you would like, please let me know.
cyberduck.log
Describe the bug
I get the
The bucket does not allow ACLserror when copying or moving files from one AWS S3 bucket to another. The destination bucket has ACLs disabled but the source does not. I've tried setting Default ACL to various values, including None, but still get the same error. There was work to address this issue in the past, e.g. #13386, which is where I first commented on this.To Reproduce
Steps to reproduce the behavior:
enforcedpreferredpreferredand set the ACL to allow public readpreferredtoenforcedExpected behavior
I would expect Cyberduck to detect that the destination has disabled ACLs and so these should not be set after the file contents have been copied.
Screenshots

Desktop (please complete the following information):
Log Files
I've added a debug log file, but tried to clean any details that are not necessary to debug this, like secrets and names of items. If there are details missing that you would like, please let me know.
cyberduck.log