[DOCS-16064] Missing details on CMK creation on encrypted snapshot Created: 24/Apr/23 Updated: 13/Dec/23 Resolved: 11/May/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Unique Wachepa | Assignee: | Will Pierce |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 41 weeks, 2 days ago |
| Description |
|
Hi Team, The KB article on How do I run a cross project automated restore for an Atlas cluster with Encryption at Rest? mentions that the AWS KMS for both clusters should be the same when restoring from a different project: >Configure Encryption at Rest with Customer Master Key (CMK) in the target project using the same value as the AWS KMS key in the source project. However, this is not mentioned in our documentation on Restore from a Snapshot Using Encryption at Rest. It only states that the same encryption provider key should be used: >Atlas can only restore to a cluster that uses the same encryption provider as the source cluster. Please let me know if I missed somewhere where this is addressed in the docs. Request Can the above be clarified in the docs to avoid customer confusion?
|