EMR File System Client-side Encryption Using AWS KMS-managed Keys Reviews

Enrique D. · Reviewed בערך 9 שנים ago

Russell P. · Reviewed בערך 9 שנים ago

Phil S. · Reviewed בערך 9 שנים ago

Aakanksha S. · Reviewed בערך 9 שנים ago

Chung Wing S. · Reviewed בערך 9 שנים ago

In putty my text was not displayed as encrypted

Abhishek S. · Reviewed בערך 9 שנים ago

Tzoori T. · Reviewed בערך 9 שנים ago

Good real world example.

Isaac S. · Reviewed בערך 9 שנים ago

Thomas G. · Reviewed בערך 9 שנים ago

Excellent lab. No issues.

Joe M. · Reviewed בערך 9 שנים ago

Pretty crap

mohammed a. · Reviewed בערך 9 שנים ago

James F. · Reviewed בערך 9 שנים ago

Jeffrey N. · Reviewed בערך 9 שנים ago

Anthony T. · Reviewed בערך 9 שנים ago

mark i. · Reviewed בערך 9 שנים ago

Sergey P. · Reviewed בערך 9 שנים ago

Tetsuhito Y. · Reviewed בערך 9 שנים ago

Mia A. · Reviewed בערך 9 שנים ago

S. V. · Reviewed בערך 9 שנים ago

Jonathan G. · Reviewed בערך 9 שנים ago

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. · Reviewed בערך 9 שנים ago

Stephen G. · Reviewed בערך 9 שנים ago

helpful

旭阳 姜. · Reviewed בערך 9 שנים ago

Jerry C. · Reviewed בערך 9 שנים ago

Mark K. · Reviewed בערך 9 שנים ago