{"id":31223,"date":"2017-02-07T01:41:49","date_gmt":"2017-02-07T06:41:49","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/new-amazon-s3-server-side-encryption-for-data-at-rest.php"},"modified":"2017-02-07T01:41:49","modified_gmt":"2017-02-07T06:41:49","slug":"new-amazon-s3-server-side-encryption-for-data-at-rest","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/new-amazon-s3-server-side-encryption-for-data-at-rest.php","title":{"rendered":"New  Amazon S3 Server Side Encryption for Data at Rest &#8230;"},"content":{"rendered":"<p><p>by Jeff Barr | on 04 OCT 2011 | in Amazon S3 | Permalink |  <\/p>\n<p>    A lot of technical tasks that seem simple in theory are often    very complex to implement. For example, lets say that you want    to encrypt all of the data that you store in Amazon S3. You    need to choose an encryption algorithm, create and store keys    (while keeping the keys themselves safe from prying eyes), and    bottleneck your code to ensure that encryption happens as    part of every PUT operation and decryption happens as part of    every GET operation. You must take care to store the keys in    durable fashion, lest you lose them along with access to your    encrypted data.  <\/p>\n<p>    In order to save you from going through all of this trouble    (and to let you focus on your next killer app), we have    implemented Server Side Encryption (SSE) for    Amazon S3    to make it easier for you to store your data in encrypted form.    You can now request encrypted storage when you store a new    object in Amazon S3 or when you copy an existing object. We    believe that this important (and often-requested) new feature    will be welcomed by our enterprise customers, perhaps as part    of an overall strategy to encrypt sensitive data for regulatory    or compliance reasons.  <\/p>\n<p>    Amazon S3 Server Side Encryption handles all encryption,    decryption, and key management in a totally transparent    fashion. When you PUT an object and request encryption (in an    HTTP header supplied as part of the PUT), we generate a unique    key, encrypt your data with the key, and then encrypt the key    with a master key. For added protection, keys are stored in    hosts that are separate and distinct from those used to store    your data. Heres a diagram of the PUT process for a request    that specifies SSE:  <\/p>\n<p>    Decryption of the encrypted data requires no effort on your    part. When you GET an encrypted object, we fetch and decrypt    the key, and then use it to decrypt your data. We also include    an extra header in the response to the GET to let you know that    the data was stored in encrypted form in Amazon S3.  <\/p>\n<p>    We encrypt your data using 256-bit AES encryption, also known    as AES-256, one of the strongest block ciphers    available. You can apply encryption to data stored using Amazon    S3s Standard or Reduced Redundancy Storage options. The entire    encryption, key management, and decryption process is inspected    and verified internally on a regular basis as part of our    existing audit process.  <\/p>\n<p>    You can use Amazon S3s bucket policies to allow, mandate, or    forbid encryption at the bucket or object level. You can use    the AWS    Management Console to upload and access encrypted objects.  <\/p>\n<p>    To learn more, check out the Using Encryption section of the Amazon S3    Developer Guide.  <\/p>\n<p>     Jeff;  <\/p>\n<p>    PS  Theres no additional charge for SSE.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read more:<br \/>\n<a target=\"_blank\" href=\"https:\/\/aws.amazon.com\/blogs\/aws\/new-amazon-s3-server-side-encryption\/\" title=\"New  Amazon S3 Server Side Encryption for Data at Rest ...\">New  Amazon S3 Server Side Encryption for Data at Rest ...<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> by Jeff Barr | on 04 OCT 2011 | in Amazon S3 | Permalink | A lot of technical tasks that seem simple in theory are often very complex to implement. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-31223","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31223"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=31223"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31223\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}