A company wants to encrypt sensitive documents stored in an Amazon S3 bucket using AWS Key Management Service (AWS KMS). The security team requires the use of a customer managed key that must be rotated automatically every year. The solutions architect must ensure that previously uploaded documents can still be decrypted after key rotation without any manual re-encryption. Which TWO actions should the solutions architect take to meet these requirements?
- Enable automatic key rotation on the AWS KMS customer managed key.Answer
- Configure the Amazon S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS) using the customer managed key.Answer
- CRe-encrypt all existing S3 objects with the new key version immediately after rotation.
- DStore the key policy administrative credentials as a plaintext parameter in Systems Manager Parameter Store.
- EConfigure the key rotation task to run under the AWS account root user credentials.
Answer
Enable automatic key rotation on the customer managed key and configure the S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS).
Enabling automatic key rotation on the customer managed key ensures that the key material is rotated annually without manual configuration. Configuring the S3 bucket to use SSE-KMS with the customer managed key ensures all documents uploaded to the bucket are secure. When KMS key rotation occurs, AWS KMS retains the historical key material so that older files can still be decrypted seamlessly.
Step-by-Step Solution
Key Concept
AWS KMS automatic key rotation updates the backing key material annually, while retaining older versions of the key material to allow the seamless decryption of historical data.
Estimated Time:1m 0s