EMR File System Client-side Encryption Using AWS KMS-managed Keys avaliações

Enrique D. · Revisado há about 9 years

Russell P. · Revisado há about 9 years

Phil S. · Revisado há about 9 years

Aakanksha S. · Revisado há about 9 years

Chung Wing S. · Revisado há about 9 years

In putty my text was not displayed as encrypted

Abhishek S. · Revisado há about 9 years

Tzoori T. · Revisado há about 9 years

Good real world example.

Isaac S. · Revisado há about 9 years

Thomas G. · Revisado há about 9 years

Excellent lab. No issues.

Joe M. · Revisado há about 9 years

Pretty crap

mohammed a. · Revisado há about 9 years

James F. · Revisado há about 9 years

Jeffrey N. · Revisado há about 9 years

Anthony T. · Revisado há about 9 years

mark i. · Revisado há about 9 years

Sergey P. · Revisado há about 9 years

Tetsuhito Y. · Revisado há about 9 years

Mia A. · Revisado há about 9 years

S. V. · Revisado há about 9 years

Jonathan G. · Revisado há 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. · Revisado há about 9 years

Stephen G. · Revisado há about 9 years

helpful

旭阳 姜. · Revisado há about 9 years

Jerry C. · Revisado há about 9 years

Mark K. · Revisado há about 9 years