We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bc6d0fa created the issue
Add support for S3 SSE-KMS (see: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html). This would enable users to input their KMS Key Id, and Cyberduck can send this key id as part of the upload request.
In the context of AWS CLI commands, you can check out this documentation: http://docs.aws.amazon.com/cli/latest/reference/s3api/put-object.html
You can specify the KMS Key Id by using --ssekms-key-id parameter.
The text was updated successfully, but these errors were encountered:
@dkocher commented
In ce0f78b. Currently there is no option to select a key but the default key configured in KMS.
Sorry, something went wrong.
We plan to add support to select specific keys to use per bucket in a later version.
Allow selection of encrypstion keys managed in AWS-KMS in 31caffd.
dkocher
No branches or pull requests
Add support for S3 SSE-KMS (see: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html). This would enable users to input their KMS Key Id, and Cyberduck can send this key id as part of the upload request.
In the context of AWS CLI commands, you can check out this documentation: http://docs.aws.amazon.com/cli/latest/reference/s3api/put-object.html
You can specify the KMS Key Id by using --ssekms-key-id parameter.
The text was updated successfully, but these errors were encountered: