关于“EMR File System Client-side Encryption Using AWS KMS-managed Keys”的评价

Enrique D. · 已于 about 9 years前审核

Russell P. · 已于 about 9 years前审核

Phil S. · 已于 about 9 years前审核

Aakanksha S. · 已于 about 9 years前审核

Chung Wing S. · 已于 about 9 years前审核

In putty my text was not displayed as encrypted

Abhishek S. · 已于 about 9 years前审核

Tzoori T. · 已于 about 9 years前审核

Good real world example.

Isaac S. · 已于 about 9 years前审核

Thomas G. · 已于 about 9 years前审核

Excellent lab. No issues.

Joe M. · 已于 about 9 years前审核

Pretty crap

mohammed a. · 已于 about 9 years前审核

James F. · 已于 about 9 years前审核

Jeffrey N. · 已于 about 9 years前审核

Anthony T. · 已于 about 9 years前审核

mark i. · 已于 about 9 years前审核

Sergey P. · 已于 about 9 years前审核

Tetsuhito Y. · 已于 about 9 years前审核

Mia A. · 已于 about 9 years前审核

S. V. · 已于 about 9 years前审核

Jonathan G. · 已于 about 9 years前审核

Lab didn't function correctly - got error on the confirm encrypted txt retrieval form s3: [hadoop@ip-172-31-13-47 ~]$ aws s3 cp s3://emr-seclab-bucket/outputfile.txt encryptedOutputFile.txt download failed: s3://emr-seclab-bucket/outputfile.txt to ./encryptedOutputFile.txt An error occurred (InvalidArgument) when calling the GetObject operation: Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4. You can enable AWS Signature Version 4 by running the command: aws configure set s3.signature_version s3v4 After executing the requested command, I could read the cleartext, I assume because s3 supports transparent decryption for users who have access to the key.

Dale B. · 已于 about 9 years前审核

Stephen G. · 已于 about 9 years前审核

helpful

旭阳 姜. · 已于 about 9 years前审核

Jerry C. · 已于 about 9 years前审核

Mark K. · 已于 about 9 years前审核