menu

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

Go to Lab

606 Reviews

83a2552c90367027d2170fffd43f7df8

Fred K. · Reviewed 4 months ago

Cc02cce9c2eaabc60d10510c81ce873a

Miroslav M. · Reviewed 4 months ago

725c3fc4d74982b33c4597d509b25532

Young Y. · Reviewed 4 months ago

5c4ac1f0db30471ab21c5b4321d70325

Randy Y. · Reviewed 4 months ago

163e6983a1077a43be1b394ae3f133c9

Marlon S. · Reviewed 4 months ago

5bfb3a706fb9a46da7a10b4c16207793

step 83: hadoop fs -put dan.txt s3://emr-seclab-bucket-dwp-2017-08-27/ 17/08/27 18:55:14 INFO s3n.MultipartUploadOutputStream: close closed:false s3://emr-seclab-bucket-dwp-2017-08-27/dan.txt 17/08/27 18:55:15 INFO s3n.MultipartUploadOutputStream: close closed:true s3://emr-seclab-bucket-dwp-2017-08-27/dan.txt step 84: $ aws s3 cp s3://emr-seclab-bucket-dwp-2017-08-27/dan.txt encrypted_dan.txt download failed: s3://emr-seclab-bucket-dwp-2017-08-27/dan.txt to ./encrypted_dan.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

Daniel P. · Reviewed 4 months ago

740c964e4bd7f6aeb06678b237cecc95

Aaron P. · Reviewed 4 months ago

9c447490d00dc5b31dcd288b88cfa090

Extremely Satisfied

Vaidyanath D. · Reviewed 4 months ago

E0cef92522911006175c1b7089280827

Ken W. · Reviewed 4 months ago

23d79d398bbee844b06e8691a339ebc5

First time I really use EMR, I wonder if it could have more developped use cases from a security view

Aristide B. · Reviewed 4 months ago

A13e873c8f191f286972334f5d026c5c

Christian S. · Reviewed 4 months ago

5afe9772bdf5b0d50688a04af38ec701

Steve J. · Reviewed 4 months ago

9fb27c91efd2d30a87e3a608583fb06e

craig s. · Reviewed 4 months ago

A637e14979bc118e0fb991b3a7de4ca6

Jean K. · Reviewed 4 months ago

105a709ffcaef0456af667e34f9ffda9

Christopher C. · Reviewed 4 months ago

0a430e2ee4b09b49507895a9b7e3cad2

sungmin h. · Reviewed 4 months ago

C407509372ecf5fa1a588e9c8fe99dec

Mariah M. · Reviewed 4 months ago

15193ec6188593971481a357dacc0568

Tom T. · Reviewed 4 months ago

F38beaebdd5d1fc7abacc02d77184630

Last bit didn't work

Tim W. · Reviewed 4 months ago

40a1b595a1c2eaf715724c01a4eb36d7

the lab instructions/observations are outdated. here's what my console gave me: [hadoop@ip-172-31-10-117 ~]$ aws s3 cp s3://emr-seclab-bucket-oley/outputFile.txt encryptedOutputFile.txt download failed: s3://emr-seclab-bucket-oley/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 [hadoop@ip-172-31-10-117 ~]$ aws configure set s3.signature_version s3v4 [hadoop@ip-172-31-10-117 ~]$ aws s3 cp s3://emr-seclab-bucket-oley/outputFile.txt encryptedOutputFile.txt download: s3://emr-seclab-bucket-oley/outputFile.txt to ./encryptedOutputFile.txt [hadoop@ip-172-31-10-117 ~]$ cat encryptedOutputFile.txt I am currently working on AWS Security Lab from Qwiklabs.

Olga B. · Reviewed 4 months ago

F5c86f3abbf9e876e5e288b3a267f14a

Kenneth W. · Reviewed 4 months ago

D2dcce1d9162ac476d8f28ea6846a54f

Way to easy.

Joerg J. · Reviewed 4 months ago

B1a664d31faffac1d87e8eb56413d602

I tried to do this lab twice and got stuck at the same place. It tells you create the encryption keys, but the labels don't match the instructions and the values you are to select don;t appear in the drop down.

Tom G. · Reviewed 4 months ago

104fa9e9c23e57062591bf3cfc4587e6

Francois B. · Reviewed 4 months ago

75d792e05cfb142a4d26502002c3b117

Ram B. · Reviewed 4 months ago