A company is migrating an application from an on-premises environment to AWS. The application will store sensitive data in Amazon S3. The company must encrypt the data before storing the data in Amazon S3. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Encrypt the data by using client-side encryption with customer managed keys.
Most accepted answer: A. Encrypt the data by using client-side encryption with customer managed keys.
Community votes: A=4, B=1, D=1
Selected Answer: A KEY: "must encrypt the data before storing the data in Amazon S3" - This means the data must be encrypted before it reaches S3. - That immediately points to client-side encryption. upvoted 1 times
Selected Answer: D For D is the answer...where it says the customer has their owns keys??? Here it is the explanation... Client-side encryption with Amazon S3 involves encrypting data on the client-side (your application) before uploading it to Amazon S3. This provides an extra layer of security as the data is encrypted before it ever leaves your control. When using S3 managed keys for client-side encryption, the key material and encryption key are managed by AWS, but the encryption process itself is handled by the S3 Encryption Client within your application upvoted 2 times
Selected Answer: A Question is unclear. "before" store= before send api or before save? upvoted 2 times
To meet the requirement of encrypting sensitive data before storing it in Amazon S3, the company should use Server-Side Encryption with Customer-Provided Keys (SSE-C) or Client-Side Encryption. However, the most common and effective approach in AWS is Server-Side Encryption with AWS Key Management Service (SSE-KMS). upvoted 1 times
Selected Answer: A If the answer is B, how will the data be encrypted before being stored in Amazon S3? It has to be client-side encryption. upvoted 2 times