Subscribe to Email Updates

    encryption Knowledge Base | 1 min read

    SSE Usages recommandations

    SSE Usage recommendations


    Well know situation : 

    You don't specify a file with a 32 char key

     

    Situation : The SSE required a 32 char key to be able to encrypt the contents which are sent to the bucket. Make sure that you include a 32 char key for having the feature working properly.

     

    Keys rotation


    Situation : The uploader key file can include multiple keys, be careful about the syntax and file organization :

    • first line is always the main encryption / decryption key
    • second lines are always the decryption keys

    Example : If you want to change the key every month (for encryption), you will store the last key in the first line, and store all previous keys in the next lines ; this to keep the possibility to decrypt the files which have been stored and encrypted with this key.
    Bucket Encryption Configuration Changes

    Situation : You store data in a bucket from a while and after a certain time, you decide to set an encryption option.

    This change only impact the new data which will be encrypted and keep all previous written files not encrypted.

    Encryption Visualization

    In an S3 object storage supporting SSE, we can easily see icons showing the encrypted files :

    key sse example


          



    Related Categories

    encryption Knowledge Base

    You may also like:

    encryption S3

    Setup SSE to encrypt S3 Buckets

    Description S3 connector is compatible with the Server-side encryption. This encryption solution is about protecting dat...

    Let Us Know What You Thought about this Post.

    Put your Comment Below.

    Learn and grow with award-winning support and a thriving community behind you.

    Get the free version