Skip to content
New issue

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

Option to use AWS KMS–Managed Keys (SSE-KMS) for server side encryption #9426

Closed
cyberduck opened this issue Apr 8, 2016 · 3 comments
Closed
Assignees
Labels
feature fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Apr 8, 2016

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.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 22, 2016

@dkocher commented

In ce0f78b. Currently there is no option to select a key but the default key configured in KMS.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 22, 2016

@dkocher commented

We plan to add support to select specific keys to use per bucket in a later version.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 21, 2016

@dkocher commented

Allow selection of encrypstion keys managed in AWS-KMS in 31caffd.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants