Overview of Mechanisms
We have all seen in the media numerous occurrences whereby large international organizations have had their data exposed and leaked that had been stored on S3. Any sensitive data stored in the cloud MUST be encrypted, and when storing your data on S3 there are multiple different options that you can choose from to enable you to protect your data with encryption. To help you understand these mechanisms, this course will guide you through the process of how each of them works, not just from an encryption perspective but also at a decryption level. This will allow you to make the right choice when it comes to selecting the most appropriate method of encryption to align with your own internal security strategy.
Applying encryption is a simple task and it can protect you and your customers from data exposure should a malicious user gain access to your S3 buckets.
If you have thoughts or suggestions for this course, please contact Cloud Academy at email@example.com.
By the end of this course series you will be able to explain the encryption and decryption process for:
- Server-Side Encryption with S3 Managed Keys (SSE-S3)
- Server-Side Encryption with KMS Managed Keys (SSE-KMS)
- Server-Side Encryption with Customer Provided Keys (SSE-C)
- Client-Side Encryption with KMS Managed Keys (CSE-KMS)
- Client-Side Encryption with Customer Provided Keys (CSE-C)
This course is intended for those who have the responsibility of storing, managing, and protecting data that is stored on Amazon S3.
This is an advanced level course and so it is essential that you have an understanding of S3 and that you have the knowledge to enable you to upload and retrieve data along with how to select different encryption options. In addition to this, you must also be familiar with the KMS service and understand both CMKs and Data encryption keys.
Server-Side Encryption with Customer Provided Keys, SSE-C. The encryption process is as follows. Firstly, a client uploads Object Data and the Customer-provided Key to S3 for a HTTPS. It will only work with the HTTPS connection. Otherwise, S3 will reject it. S3 will then use the Customer-provided Key to encrypt the Object Data. S3 will also create a sorted HMAC value of the Customer-provided Key for future validation requests. The encrypted Object Data, along with the HMAC value of the Customer Key is then saved and stored on S3. The Customer-provided Key is then removed from memory. The decryption process is as follows. A request is made by the client via HTTPS connection to S3 to retrieve the Object Data. At the same time, the Customer-provided Key is also sent with the request. S3 uses the HMAC value of the same key to confirm it's validity of the requested object. The Customer-provided Key is then used to decrypt the encrypted Object Data. The Object Data is then sent back to the client.
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.