You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/04/13 17:59:41 UTC
[jira] [Commented] (HADOOP-13075) Add support for SSE-KMS and SSE-C
in s3a filesystem
[ https://issues.apache.org/jira/browse/HADOOP-13075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967967#comment-15967967 ]
Steve Loughran commented on HADOOP-13075:
-----------------------------------------
Remind me, why are these tests not running in the parallel block? It's adding to over a minute to every test run
{code}
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.864 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEC
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSECBlockOutputStream
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.373 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSECBlockOutputStream
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSDefaultKey
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.648 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSDefaultKey
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSUserDefinedKey
Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.011 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSUserDefinedKey
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSUserDefinedKeyBlockOutputStream
Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.01 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSEKMSUserDefinedKeyBlockOutputStream
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSES3
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.573 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSES3
Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSES3BlockOutputStream
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.156 sec - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSES3BlockOutputStream
{code}
> Add support for SSE-KMS and SSE-C in s3a filesystem
> ---------------------------------------------------
>
> Key: HADOOP-13075
> URL: https://issues.apache.org/jira/browse/HADOOP-13075
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Andrew Olson
> Assignee: Steve Moist
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HADOOP-13075-001.patch, HADOOP-13075-002.patch, HADOOP-13075-003.patch, HADOOP-13075-branch2.002.patch
>
>
> S3 provides 3 types of server-side encryption [1],
> * SSE-S3 (Amazon S3-Managed Keys) [2]
> * SSE-KMS (AWS KMS-Managed Keys) [3]
> * SSE-C (Customer-Provided Keys) [4]
> Of which the S3AFileSystem in hadoop-aws only supports opting into SSE-S3 (HADOOP-10568) -- the underlying aws-java-sdk makes that very simple [5]. With native support in aws-java-sdk already available it should be fairly straightforward [6],[7] to support the other two types of SSE with some additional fs.s3a configuration properties.
> [1] http://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html
> [2] http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html
> [3] http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html
> [4] http://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html
> [5] http://docs.aws.amazon.com/AmazonS3/latest/dev/SSEUsingJavaSDK.html
> [6] http://docs.aws.amazon.com/AmazonS3/latest/dev/kms-using-sdks.html#kms-using-sdks-java
> [7] http://docs.aws.amazon.com/AmazonS3/latest/dev/sse-c-using-java-sdk.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org