S3 encryption options in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding S3 Server-Side Encryption Types

Which S3 server-side encryption option uses AWS Key Management Service (KMS) to manage encryption keys?

A SSE-KMS (encryption with keys managed in AWS KMS)

B SSE-S3 (AES-256 encryption managed by Amazon S3)

C SSE-C (customer-provided encryption keys)

D Client-side encryption before uploading

💡 Hint

Think about which option integrates with AWS KMS for key management.

SSE-KMS uses AWS Key Management Service to manage encryption keys, providing additional control and audit capabilities compared to SSE-S3.

❓ service_behavior

intermediate

S3 Bucket Default Encryption Behavior

If you enable default encryption on an S3 bucket with SSE-S3, what happens when a new object is uploaded without specifying encryption?

A The object is stored unencrypted.

B The upload fails with an error.

C The object is encrypted using SSE-KMS automatically.

D The object is encrypted using SSE-S3 automatically.

💡 Hint

Consider the effect of default encryption settings on new uploads.

When default encryption is enabled with SSE-S3, all new objects are encrypted automatically using SSE-S3 if no encryption is specified.

❓ Configuration

advanced

Configuring S3 Bucket Policy for Enforcing Encryption

Which bucket policy condition enforces that all PUT requests must use SSE-KMS encryption?

A "Condition": {"Bool": {"aws:SecureTransport": "false"}}

B "Condition": {"StringEquals": {"s3:x-amz-server-side-encryption": "AES256"}}

C "Condition": {"StringEquals": {"s3:x-amz-server-side-encryption": "aws:kms"}}

D "Condition": {"StringNotEquals": {"s3:x-amz-server-side-encryption": "aws:kms"}}

💡 Hint

Look for the condition that matches SSE-KMS encryption header.

The condition with "s3:x-amz-server-side-encryption": "aws:kms" ensures that PUT requests use SSE-KMS encryption.

❓ security

advanced

Security Implications of SSE-C Encryption

What is a key security responsibility when using SSE-C (server-side encryption with customer-provided keys) in S3?

A No encryption keys are needed because encryption is client-side.

B You must securely manage and provide the encryption key with each request.

C Encryption keys are stored in AWS KMS for auditing.

D AWS manages and rotates the encryption keys automatically.

💡 Hint

Think about who controls the keys in SSE-C.

With SSE-C, the customer provides the encryption key with each request and is responsible for managing it securely. AWS does not store the key.

❓ Architecture

expert

Choosing Encryption for Compliance and Audit Needs

Your company requires detailed audit logs for encryption key usage and wants to control key rotation policies. Which S3 encryption option best meets these requirements?

A SSE-KMS with customer-managed keys in AWS KMS

B SSE-S3 with default Amazon-managed keys

C SSE-C with customer-provided keys

D Client-side encryption before uploading

💡 Hint

Consider which option offers audit logs and key rotation control.

SSE-KMS with customer-managed keys allows detailed audit logging and key rotation control via AWS KMS, meeting compliance needs.

Practice

1. What does enabling default encryption on an S3 bucket do?

easy

A. Allows only public access to the bucket

B. Deletes unencrypted objects from the bucket

C. Prevents any uploads to the bucket

D. Automatically encrypts all objects uploaded to the bucket

Solution

1. Step 1: Understand default encryption purpose

   Default encryption ensures all new objects are encrypted automatically when uploaded.

2. Step 2: Analyze options

   Only Automatically encrypts all objects uploaded to the bucket describes automatic encryption of all uploads, others describe unrelated or incorrect behaviors.

3. Final Answer:

   Automatically encrypts all objects uploaded to the bucket -> Option D

4. Quick Check:

   Default encryption = automatic encryption [OK]

Hint: Default encryption means all uploads get encrypted automatically [OK]

Common Mistakes:

• Thinking encryption deletes files
• Confusing encryption with access control
• Believing encryption blocks uploads

2. Which of the following is the correct way to specify AES256 server-side encryption in an S3 PutObject API call?

easy

A. "ServerSideEncryption": "AES256"

B. "Encryption": "SSE-S3"

C. "EncryptionMethod": "AES256"

D. "ServerSideEncryption": "aws:kms"

Solution

1. Step 1: Recall correct parameter name and value

   The correct parameter is ServerSideEncryption with value "AES256" for AWS-managed keys.

2. Step 2: Check options

   "ServerSideEncryption": "AES256" matches the exact syntax; others use wrong keys or values.

3. Final Answer:

   "ServerSideEncryption": "AES256" -> Option A

4. Quick Check:

   Correct key and value for AES256 = "ServerSideEncryption": "AES256" [OK]

Hint: Use ServerSideEncryption: AES256 for simple AWS-managed encryption [OK]

Common Mistakes:

• Using wrong parameter names
• Confusing KMS and AES256 values
• Using unsupported encryption keys

3. Given this AWS CLI command to upload a file with KMS encryption:
aws s3 cp file.txt s3://mybucket/ --sse aws:kms --sse-kms-key-id 1234abcd-12ab-34cd-56ef-1234567890ab
What will happen if the KMS key ID is invalid?

medium

A. The file uploads with AES256 encryption instead

B. The file uploads without encryption

C. The upload fails with an error

D. The file uploads but is inaccessible

Solution

1. Step 1: Understand KMS key validation

   AWS checks the KMS key ID during upload; if invalid, it rejects the request.

2. Step 2: Analyze upload behavior on invalid key

   Upload fails with an error because encryption cannot proceed without a valid key.

3. Final Answer:

   The upload fails with an error -> Option C

4. Quick Check:

   Invalid KMS key = upload error [OK]

Hint: Invalid KMS key causes upload failure, not fallback [OK]

Common Mistakes:

• Assuming fallback to AES256
• Thinking upload succeeds without encryption
• Believing file becomes inaccessible silently

4. You configured an S3 bucket with default encryption using AWS KMS, but uploads from your app fail with an AccessDenied error. What is the most likely cause?

medium

A. The app lacks permission to use the KMS key

B. The bucket policy denies all uploads

C. The app is uploading unencrypted files

D. The bucket encryption is disabled

Solution

1. Step 1: Understand KMS permission requirements

   Using KMS encryption requires the uploader to have permission to use the KMS key.

2. Step 2: Analyze error cause

   AccessDenied during upload with KMS encryption usually means missing KMS key permissions.

3. Final Answer:

   The app lacks permission to use the KMS key -> Option A

4. Quick Check:

   KMS permission missing = AccessDenied error [OK]

Hint: Check KMS key permissions if AccessDenied on encrypted upload [OK]

Common Mistakes:

• Assuming bucket policy denies uploads
• Ignoring KMS key permissions
• Thinking encryption is disabled

5. You want to ensure all objects in your S3 bucket are encrypted using your own KMS key, but also want to allow some users to upload unencrypted files temporarily. Which approach is best?

hard

A. Enable default bucket encryption with your KMS key and use a bucket policy to deny unencrypted uploads

B. Enable default encryption with your KMS key and use a bucket policy that allows unencrypted uploads only for specific users

C. Enable default encryption with your KMS key and create an IAM policy allowing specific users to bypass encryption

D. Do not enable default encryption and require users to specify encryption manually

Solution

1. Step 1: Understand default encryption and exceptions

   Default encryption applies to all uploads unless bucket policy allows exceptions.

2. Step 2: Analyze options for allowing unencrypted uploads temporarily

   Bucket policies can allow unencrypted uploads for specific users while default encryption is enabled.

3. Step 3: Evaluate options

   Enable default encryption with your KMS key and use a bucket policy that allows unencrypted uploads only for specific users correctly uses bucket policy exceptions; Enable default bucket encryption with your KMS key and use a bucket policy to deny unencrypted uploads denies unencrypted uploads completely; Do not enable default encryption and require users to specify encryption manually lacks default encryption; Enable default encryption with your KMS key and create an IAM policy allowing specific users to bypass encryption cannot bypass encryption via IAM policy.

4. Final Answer:

   Enable default encryption with your KMS key and use a bucket policy that allows unencrypted uploads only for specific users -> Option B

5. Quick Check:

   Bucket policy exceptions allow controlled unencrypted uploads [OK]

Hint: Use bucket policy exceptions to allow unencrypted uploads with default encryption [OK]

Common Mistakes:

• Thinking IAM policies can bypass bucket encryption
• Disabling default encryption to allow exceptions
• Denying all unencrypted uploads without exceptions