Cloud Zone is brought to you in partnership with:

I am the API Evangelist. Not in the sense that I’m evangelizing a single API to you--In the sense that APIs are important for everyone to be aware of. I’m paying attention to not just the technical, but the business and politics of the web API movement. I share my insights by blogging on the business of APIs at apievangelist.com, politics of APIs at apivoice.com and you can find more information about me at kinlane.com. Kin is a DZone MVB and is not an employee of DZone and has posted 72 posts at DZone. You can read more from them at their website. View Full User Profile

Amazon Web Services Offers Server Side Encryption for Amazon S3

10.10.2011
| 2289 views |
  • submit to reddit

Amazon Web Services now offers Server Side Encryption (SSE) for Amazon S3, enabling the ability to encrypt data stored in Amazon S3, by adding an additional request header when writing the object to Amazon S3, with decryption occurring automatically when data is retrieved.

Amazon S3 Server Side Encryption employs multi-factor encryption, with each object encrypted with a unique key, and as an additional safeguard, this key is itself encrypted with a regularly rotated master key. Amazon S3 Server Side Encryption uses one of the strongest block ciphers available — 256-bit Advanced Encryption Standard (AES-256).

You can start using Amazon S3 Server Side Encryption in the AWS Management Console:

  1. Under the Amazon S3 tab, use the upload dialog to add files to be uploaded.
  2. In the “Set Details” section of the upload dialog, set the “Use Server Side Encryption” checkbox property.
  3. Start Upload. The files will be encrypted and stored in Amazon S3.

If you prefer to manage your own encryption keys, you can also make use of the client libraries for encryption provided by Amazon. To learn more, visit the Amazon S3 Encryption client page.

 

From http://www.kinlane.com/2011/10/amazon-web-services-offers-server-side-encryption-for-amazon-s3/

Published at DZone with permission of Kin Lane, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)