Kuali S3 Bucket params

4 views
Skip to first unread message

Tara, Hitesh

unread,
Apr 10, 2018, 9:48:47 AM4/10/18
to kc.techni...@kuali.org

Hi All ,

 

Does Any one know about the last param of encryption file.How do we set up that.

 

<param name="s3.bucket.name">kuali-attachment</param>

       <param name="s3.region">us-east-1</param>

       <param name="s3.access.key">AKIAILGEPFFFJULUEYFxxxQS7Q</param>

       <param name="s3.secret.key">2FcSxGmoopUFFF65xV7mIvfoov6O5QD6xxxxxxt</param>

       <param name="s3.encryption.key.file"></param>

I  have used the following code Using SDK with a defined bucket policy. Any Advice will be welcome

 

Thanks

Hitesh

 

 PutObjectRequest putRequest1 = new PutObjectRequest(newBucketName, "encrypted/" + fileName + "." + System.currentTimeMillis(), file);

            ObjectMetadata objectMetadata1 = new ObjectMetadata();

            objectMetadata1.setSSEAlgorithm(ObjectMetadata.AES_256_SERVER_SIDE_ENCRYPTION);

            putRequest1.setMetadata(objectMetadata1);

 

 

            PutObjectResult response1 = s3Client.putObject(putRequest1);

            System.out.println("Uploaded object encryption status is " +

                    response1.getSSEAlgorithm());

        }

Doug Pace

unread,
Apr 10, 2018, 11:46:29 AM4/10/18
to Tara, Hitesh, kc.techni...@kuali.org
Hitesh -

That parameter was used for client side encryption, meaning the file would be encrypted using a local key before being uploaded to S3. We've deprecated this and moved to using server side encryption, similar to the code sample you've included. Client side encryption was slightly more secure, but came at the risk of the key being lost or corrupted and all attachments becoming inaccessible.

--
You received this message because you are subscribed to the Google Groups "KC Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kc.technical.co...@kuali.org.
--
Kuali logo
Douglas Pace 
Engineering Manager
801-922-0408 
kuali.co
  
Best place to work 2016
Reply all
Reply to author
Forward
0 new messages