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
I configured SSE-S3 (AES-256) on Preference, and then tried to use Server Side Encryption (SSE), but it seems SSE is invalid for my bucket/object. I only read and configured as follows documentation.
According to cyberduck debug logging (defaults write ch.sudo.cyberduck logging debug), I wonder x-amz-server-side-encryption header is not set with PUT Object API when I upload new object? My configuration might be something wrong. After uploading, I cannot change "Encryption" field in S3 tab on Info dialog for the object.
Could you confirm that SSE works on your environment and above documentation is appropriate?
The text was updated successfully, but these errors were encountered:
The documentation should be correct. You can either select the encryption setting in Preferences to use SSE for uploads by default or override these default settings in the File → Info (⌘-I) → S3 panel per bucket.
I configured SSE-S3 (AES-256) on Preference, and then tried to use Server Side Encryption (SSE), but it seems SSE is invalid for my bucket/object. I only read and configured as follows documentation.
According to cyberduck debug logging (defaults write ch.sudo.cyberduck logging debug), I wonder x-amz-server-side-encryption header is not set with PUT Object API when I upload new object? My configuration might be something wrong. After uploading, I cannot change "Encryption" field in S3 tab on Info dialog for the object.
Could you confirm that SSE works on your environment and above documentation is appropriate?
The text was updated successfully, but these errors were encountered: