Ensure that your AWS DocumentDB clusters data is encrypted with KMS Customer Master Keys (CMKs) instead of AWS managed-keys (default keys used by the DocumentDB service when there are no customer-managed keys defined) in order to have a more granular control over DocumentDB data-at-rest encryption and decryption.
This rule can help you with the following compliance standards:
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
When you use your own AWS KMS Customer Master Keys (CMKs) to protect your DocumentDB data (including indexes, logs, replicas and snapshots) from unauthorized users, you have full control over who can use the encryption keys to access your data. Amazon KMS service allows you to easily create, rotate, disable and audit Customer Master Keys created for your Amazon DocumentDB clusters.
To determine the encryption status and configuration for your AWS DocumentDB clusters, perform the following actions:
Remediation / Resolution
To encrypt an existing Amazon DocumentDB cluster with your own AWS KMS Customer Master Key (CMK), perform the following actions:
- AWS Documentation
- Amazon DynamoDB FAQs
- What Is Amazon DocumentDB (with MongoDB Compatibility)?
- Encrypting Data at Rest in Amazon DocumentDB
- Step 1: Create an Amazon DocumentDB Cluster
- Step 4: (Optional) Delete the Amazon DocumentDB Instance and Cluster
Unlock the Remediation Steps
Gain free unlimited access
to our full Knowledge Base
Over 750 rules & best practices
Get started for FREE
You are auditing:
DocumentDB Clusters Encrypted with KMS CMKs
Risk level: High