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

Roukna S. · Reviewed over 7 years ago

Syed S. · Reviewed over 7 years ago

Can't open up connection. Says Host doesn't exist. Used correct hostname

Simon G. · Reviewed over 7 years ago

I received an invalid VPC/subnet error when trying to create my cluster.

Benjamin L. · Reviewed over 7 years ago

Very Good Lab. Highlights the Security Capabilities (Client Side Encryption) while integrating various AWS services like EMR, KMS, S3, IAM, CloudFormation for the roles initial setup. And also additional Services like VPC (Route Table, NACL, Sec. Groups, EIP ..). Various Business Use Case Areas can leverage these capabilities like the financial sector and so on. Thank you. // A small note, if I could, the step 53 should state "write your file from EMR to S3" right!

fabian Z. · Reviewed over 7 years ago

Chi Z. · Reviewed over 7 years ago

Good

Caroline H. · Reviewed over 7 years ago

Tom D. · Reviewed over 7 years ago

Craig E. · Reviewed over 7 years ago

Naoki N. · Reviewed over 7 years ago

katsuya t. · Reviewed over 7 years ago

Ravikant G. · Reviewed over 7 years ago

I would have liked to understand how transparent encryption works in EMR and why the object that is written to S3 is not readable from the bucket but it is readable from EMR. Where is the client side encryption happening? Is it from the EMR cluster? What is considered the client?

Yasser Q. · Reviewed over 7 years ago

OK

Roger B. · Reviewed over 7 years ago

Benjamin H. · Reviewed over 7 years ago

Oh Jun Y. · Reviewed over 7 years ago

user o. · Reviewed over 7 years ago

5

Justo P. · Reviewed over 7 years ago

Hiura S. · Reviewed over 7 years ago

おわらなかった。

友香 木. · Reviewed over 7 years ago

kyo k. · Reviewed over 7 years ago

Shunsuke K. · Reviewed over 7 years ago

Chad L. · Reviewed over 7 years ago

Dennis W. · Reviewed over 7 years ago