New Folder with AES256 encryption #9007
Comments
Try to set the default to AES256 in Preferences → S3 → Encryption. |
This still seems to be an issue. Maybe it's very specific to my account permissions (which I cannot control), but Cyberduck throws an error and fails to create a directory where other tools (e.g. S3Browser) do not. See screenshots. |
Please post the transcript from the log drawer (⌘-L). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an AWS S3 bucket that enforces AES server-side encryption for all data. Cyberduck data transfers work fine with the encryption flag set, but trying to create a New Folder fails with an "Access Denied" error.
Using Amazon's console I could successfully create a new folder, so I compared the http headers to a folder created by Cyberduck in another bucket that doesn't enforce AES encryption. The only obvious difference is that the folder created with Amazon's tool has the "x-amz-server-side-encryption: AES256" header set while the Cyberduck-created folder does not. Can Cyberduck enforce setting this header when creating New Folders while AES256 encryption is enabled?
Attachments
Screen Shot 2015-09-14 at 5.40.06 PM.png(43.3 KiB)Screen Shot 2015-09-14 at 5.45.57 PM.png(99.6 KiB)Screen Shot 2015-09-14 at 5.48.08 PM.png(53.2 KiB)The text was updated successfully, but these errors were encountered: