Open thomascollett opened 6 years ago
Note that a full integration test would require the creation of a custom KMS key which would incur a monthly charge. Temporary keys also cannot be deleted until the cool-down period has lapsed.
Hi @thomascollett ,
I hope you're well!
I'm not sure, if you've recieved my e-mail, but just in case -- I'm reaching out here as well. As this project seems to have been abandoned, I was wondering, if you'd be interested in contributing these fixes against our spin-off (rebranded fork) -- s3fs-nio?
Kind regards,
Martin
Adds support for KMS encryption for objects in S3, by specifying the key ID to use. Closes #80 .
Key ID can be specified as an alias (e.g.
alias/mykeyaliasname
), by the key's UUID displayed in the IAM console (e.g.abcdef123-1122-3344-5566-1a23456789cd
), or by the full ARN (arn:aws:kms:eu-west-1:1234567890:key/abcdef123-1122-3344-5566-1a23456789cd
).Have tested the changes against a remote bucket with a custom key and the correct KMS encryption metadata is being set on the objects.