GitHub user natesammons-nasdaq opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/886

    [ZEPPELIN-848] Add support for encrypted data stored in Amazon S3

    ### What is this PR for?
    Adds support for using the AWS KMS or a custom encryption materials
    provider class to encrypt data stored in Amazon S3.  Also a minor
    improvement to logic inside the S3 notebook repo when dealing with local 
files.
    
    ### What type of PR is it?
    Improvement
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-848
    
    ### How should this be tested?
    Running in EMR or another system in AWS is easiest.  Make appropriate 
changes to the config and use an AWS KMS key
    
    ### Questions:
    * Does the licenses files need update? -- NO
    * Is there breaking changes for older versions? -- NO
    * Does this needs documentation? -- YES, changes in storage.md and 
zeppelin-site.xml.template


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Nasdaq/incubator-zeppelin master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-zeppelin/pull/886.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #886
    
----
commit 8628d9590f6248f0f811397db3c1af69c8aee162
Author: Nate Sammons <nate.samm...@nasdaq.com>
Date:   2016-05-11T16:06:00Z

    ZEPPELIN-848: Add support for encrypted data stored in Amazon S3
    
    Adds support for using the AWS KMS or a custom encryption materials
    provider class to encrypt data stored in Amazon S3.  Also a minor
    improvement to logic inside the S3 notebook repo.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to