Versions Compared

Old Version 2

changes.mady.by.user Aparna Tayi

Saved on

compared with

New Version 3

changes.mady.by.user Chandna Mitra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page

Table of Contents
maxLevel2
excludeOlder Versions|Additional Resources|Related Links|Related Information

SnapLogic Hadoop Snaps support encryption zones transparently. What that means is that if the HDFS cluster is configured with "Transparent at rest Encryption", our Snaps have the capability to read/write into encryption zones. 

...

  • Create an encryption key:

    Code Block
    $sudo -u <user_name> hadoop key create <key_name>



  • Create a new empty directory and make it an encryption zone using the key created above:

    Code Block
    $sudo -u hdfs hadoop fs -mkdir /encryption_zone
$sudo -u hdfs hdfs crypto -createZone -keyName <key_name> -path /encryption_zone



  • Delete encryption zones:

    Code Block
    $sudo -u hdfs hadoop fs -rm -r -skipTrash /encryption_zone


...

  • User impersonation.

    Hadoop allows you to configure proxy users to access HDFS on behalf of other users; this is called impersonation. When user impersonation is enabled on the Hadoop cluster, any jobs submitted using a proxy are executed with the impersonated user's existing privilege levels rather than those of a superuser.

    When User Impersonation option is selected and Kerberos is not selected as the account type, the user who is executing the pipeline is used to impersonate for the HDFS Operations. For example, if the user logged into the SnapLogic platform is operator@snaplogic.com, then the user name "operator" is used to proxy the super user. When a Kerberos account is configured and User impersonation is selected, the Client Principal configured in the Kerberos account impersonates the pipeline user.

    This user is expected to be in the ACL as described below,

  • Set the right acls for impersonating user to decrypt key(essentially read from encryption zone) in kms-acls.xml / KMS UI. 

    Code Block
    <property>
<name>key.acl.<key_name>.DECRYPT_EEK</name>
<value>user1,user2,userN group1,group2,groupN</value>
<description> ACL for decryptEncryptedKey operations. </description>
</property>


    Refer to the specific managed service for more information on how to do that in the UI/Configuration:

https://hadoop.apache.org/docs/r2.8.0/hadoop-kms/index.html#Decrypt_Encrypted_Key
https://www.cloudera.com/documentation/enterprise/5-8-x/topics/cdh_sg_kms_security.html#concept_fgf_42v_mp
https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.1/bk_security/content/ranger-kms-admin-guide.html


  • In Snaplex Settings, Node properties, add the value -DHADOOP_CLIENT_CONF_DIR=<conf_dir> to the key jvm_options for the "jcc.jvm_options" under Global properties.

  • Add following to the core-site.xml in cluster configuration or add it to core-site.xml located in the input directory pointed by HADOOP_CLIENT_CONF_DIR

    Code Block
    <property>
<name>hadoop.security.crypto.codec.classes.aes.ctr.nopadding</name>
<value>org.apache.hadoop.crypto.OpensslAesCtrCryptoCodec, org.apache.hadoop.crypto.JceAesCtrCryptoCodec</value>
</property>