-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-13887. Support S3 client side encryption (S3-CSE) using AWS-SDK #3292
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
Conversation
apache#2706) This (big!) patch adds support for client side encryption in AWS S3, with keys managed by AWS-KMS. Read the documentation in encryption.md very, very carefully before use and consider it unstable. S3-CSE is enabled in the existing configuration option "fs.s3a.server-side-encryption-algorithm": fs.s3a.server-side-encryption-algorithm=CSE-KMS fs.s3a.server-side-encryption.key=<KMS_KEY_ID> You cannot enable CSE and SSE in the same client, although you can still enable a default SSE option in the S3 console. * Filesystem list/get status operations subtract 16 bytes from the length of all files >= 16 bytes long to compensate for the padding which CSE adds. * The SDK always warns about the specific algorithm chosen being deprecated. It is critical to use this algorithm for ranged GET requests to work (i.e. random IO). Ignore. * Unencrypted files CANNOT BE READ. The entire bucket SHOULD be encrypted with S3-CSE. * Uploading files may be a bit slower as blocks are now written sequentially. * The Multipart Upload API is disabled when S3-CSE is active. Contributed by Mehakmeet Singh
Ran tests using mvn -Dparallel-tests -DtestsThreadCount=8 clean verify with CSE on. All good . |
CC: @steveloughran |
Added the latest CSE Tuning. Tested successfully, but would be best if someone could once run the tests once in their setup before this goes in. |
💔 -1 overall
This message was automatically generated. |
looks like a container issue. Try rebase and resubmit |
7778dce
to
a677fa1
Compare
💔 -1 overall
This message was automatically generated. |
javac error seems unrelated to the patch and check styles is as discussed indentations. |
Going to make this as the backport for only the first commit, so that we could have a chain of commits rather than 1 commit with all the others squashed. |
a677fa1
to
e421824
Compare
💔 -1 overall
This message was automatically generated. |
Merged in branch-3.3 |
Region: ap-south-1.
mvn clean verify -Dparallel-tests -DtestsThreadCount=4 -Dscale
CSE ON, S3Guard ON
CSE ON, S3Guard OFF
CSE OFF, S3Guard ON
CSE OFF, S3Guard OFF