QuestionQ66

VerifiedContinuous Improvement for Existing Solutions

A health insurance company keeps personally identifiable information (PII) in an Amazon S3 bucket. The company encrypts its objects by using server-side encryption with S3 managed encryption keys (SSE-S3). Under a new requirement, every existing and future object in the S3 bucket must be encrypted with keys managed by the company’s security team. Versioning is not enabled on the S3 bucket.

Which solution meets these requirements?

Explanation

SSE-KMS can use a customer managed AWS KMS key, allowing the security team to administer the key and its policy. Bucket default encryption ensures new objects use that encryption setting, while existing SSE-S3 objects must be rewritten to change their encryption. Re-uploading replaces each object because versioning is disabled. SSE-S3, also identified by AES256, uses Amazon S3 managed keys and cannot be configured with a customer managed key.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!