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 have encountered an issue where the new(ish) S3 default encryption (relevant doc: https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-encryption.html) which I have configured to use a specific SSE-KMS key is not being applied when Cyberduck> preferences > S3 > Encryption is set to "None". Uploads fail with the error message:
Upload <file> failed.
Access denied. Please contact your web hosting provider for assistance.
PUT /test HTTP/1.1
...
HTTP/1.1 403 Forbidden
Replication:
Create a bucket and apply an SSE-KMS default encryption
Using Cyberduck/Mountainduck attempt to upload a file
Upload fails
Could the PUT be being sent with some version of "x-amz-server-side-encryption=null" when it should simply be omitted?
I did find a workaround, which is to manually choose the correct SSE-KMS key in preferences, but this negates one of the primary benefits of having a bucket default so that all team members have the exact same config.
The text was updated successfully, but these errors were encountered:
Just checking in to say that this is still a pain point. Is there anything I can do to help this? If you share how you would like this resolved, I may be able to submit a PR in the coming weeks.
Just checking in to say that this is still a pain point. Is there anything I can do to help this? If you share how you would like this resolved, I may be able to submit a PR in the coming weeks.
Thanks!
A pull request would certainly be appreciated. From what I read in the documentation we would probably need another select option for Using Amazon S3 Bucket Keys with default encryption which would then cause the x-amz-server-side-encryption-bucket-key-enabled header to be set in the request.
I have encountered an issue where the new(ish) S3 default encryption (relevant doc: https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-encryption.html) which I have configured to use a specific SSE-KMS key is not being applied when
Cyberduck> preferences > S3 > Encryption
is set to "None". Uploads fail with the error message:Replication:
Could the PUT be being sent with some version of "x-amz-server-side-encryption=null" when it should simply be omitted?
I did find a workaround, which is to manually choose the correct SSE-KMS key in preferences, but this negates one of the primary benefits of having a bucket default so that all team members have the exact same config.
The text was updated successfully, but these errors were encountered: