SAA-C03 ยท Data protection and compliance
Encryption at rest with AWS KMS
KMS keys (AWS managed versus customer managed), envelope encryption and server-side encryption options for S3, EBS and RDS.
Key points
- AWS managed keys (aws/s3, aws/rds): rotated yearly; no policy edits or deletion.
- Customer managed keys: you control key policy, rotation, disabling, deletion.
- Envelope encryption: KMS key encrypts data key, data key encrypts data, encrypted data key is stored with data.
- S3: SSE-S3 default; SSE-KMS (S3 Bucket Key cuts KMS requests), DSSE-KMS, SSE-C.
- RDS: set at creation; existing instance: snapshot, copy with encryption, restore.
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/default-bucket-encryption.html
Practice questions
In envelope encryption with AWS KMS, which key actually encrypts the application data?
- The KMS key itself
- A data key generated by KMS
- The IAM user's access key
- The key policy document
Show answer
Answer: B. A data key generated by KMS
The data key encrypts the data; the KMS key only encrypts (wraps) the data key. KMS keys are not used to encrypt large payloads directly.
Which statements correctly compare customer managed keys with AWS managed keys in AWS KMS?
- You can edit the key policy of a customer managed key
- You can set a custom automatic rotation period on a customer managed key
- You can edit the key policy of an AWS managed key
- You can schedule an AWS managed key for deletion
- AWS managed keys are never rotated
Show answer
Answer: A. You can edit the key policy of a customer managed key, B. You can set a custom automatic rotation period on a customer managed key
Only customer managed keys let you edit the key policy and choose automatic rotation with your own period. AWS managed keys cannot be deleted by you and are rotated by AWS every year, so saying they never rotate is wrong.
Changing a bucket's default encryption to SSE-KMS automatically re-encrypts the objects already stored in it.
Show answer
Answer: False
False. Default encryption only applies to objects uploaded after the change; existing objects keep the encryption they had. Re-encrypting them needs a separate copy or batch job.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
