You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using 4.7 (17432), and users are having difficulty renaming files in our s3 bucket.
The bucket allows all permissions. It requires Server Side Encryption (SSE) to be turned on, but the files do not inherit this - when you look in Info for any given file, Server Side Encryption is unchecked.
If you try to rename a file it fails. (Cannot rename file. Access denied. Please contact your web hosting service provider for assistance.)
We've found that if you select the file you want to rename, and click Server Side Encryption in Info, it will let you rename the file once, but we have to repeat the process to rename it again.
Additionally, if we use Cloudberry's Explorer for S3 using same credentials with SSE turned on in Cloudberry we can rename the files with no difficulty - so this problem seems isolated to Cyberduck.
The text was updated successfully, but these errors were encountered:
Server side encryption is not a bucket option but per object. However I suppose you enforce encryption of objects in the bucket with a bucket policy as described in Protecting Data Using Server-Side Encryption. Make sure to enable AES2566 encryption by default in Preferences → S3 → Encryption.
Add test in a68847a.
This test shows the issue with a 403 error because no x-amz-server-side-encryption encryption header is set while the bucket policy enforces encryption.
We're using 4.7 (17432), and users are having difficulty renaming files in our s3 bucket.
The bucket allows all permissions. It requires Server Side Encryption (SSE) to be turned on, but the files do not inherit this - when you look in Info for any given file, Server Side Encryption is unchecked.
If you try to rename a file it fails. (Cannot rename file. Access denied. Please contact your web hosting service provider for assistance.)
We've found that if you select the file you want to rename, and click Server Side Encryption in Info, it will let you rename the file once, but we have to repeat the process to rename it again.
Additionally, if we use Cloudberry's Explorer for S3 using same credentials with SSE turned on in Cloudberry we can rename the files with no difficulty - so this problem seems isolated to Cyberduck.
The text was updated successfully, but these errors were encountered: