Skip to content

Added support for S3 Client Side Encryption (S3 CSE)#325

Open
sam33rch wants to merge 1 commit intodatabricks:masterfrom
sam33rch:master
Open

Added support for S3 Client Side Encryption (S3 CSE)#325
sam33rch wants to merge 1 commit intodatabricks:masterfrom
sam33rch:master

Conversation

@sam33rch
Copy link
Copy Markdown

@sam33rch sam33rch commented Feb 4, 2017

This commit adds S3 Client Side Encryption support to spark-redshfit library that allows
full end-to-end data encryption over network for read/write operations.

This commit adds S3 Client Side Encryption support to spark-redshfit library that allows
full end-to-end data encryption over network for read/write operations.
@danielsan
Copy link
Copy Markdown

This is a good one

@ghost
Copy link
Copy Markdown

ghost commented Jul 26, 2017

Agreed. We need this PR merged

@dedgsus
Copy link
Copy Markdown

dedgsus commented Sep 27, 2017

Another +1. Super useful feature.

@guruswan
Copy link
Copy Markdown

+1. Very useful feature.

@szsiddiq
Copy link
Copy Markdown

szsiddiq commented Feb 8, 2018

+1 This is a great feature - what's keeping it from being merged?

@twwildey
Copy link
Copy Markdown

+1 for this feature!

@rumeshkrish
Copy link
Copy Markdown

rumeshkrish commented Jun 11, 2020

Would it possible to add support for KMS_KEY_ID option in UNLOAD command ?

Documentation : https://docs.aws.amazon.com/redshift/latest/dg/t_unloading_encrypted_files.html

Example:

    unload ('select venuename, venuecity from venue')
    to 's3://mybucket/encrypted/venue_' 
    iam_role 'arn:aws:iam::0123456789012:role/MyRedshiftRole'
    KMS_KEY_ID '1234abcd-12ab-34cd-56ef-1234567890ab'
    encrypted;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants