[DOC-14349] Implement Encrypt at Rest - #4176
pramodkumarka-sys wants to merge 1 commit into
Conversation
| For example, Analytics log files such as `analytics_debug.log` and `analytics_periodic_dump.log` remain unencrypted even when encryption-at-rest for logs is enabled. | ||
|
|
||
| * Couchbase Server stores most XDCR metadata — remote cluster references and replication specifications — using the same mechanism as other configuration data. When you enable encryption for configuration data, Couchbase Server also encrypts this XDCR metadata. | ||
| XDCR checkpoints, collection manifests, and broken maps use a separate storage mechanism (simple_store). Couchbase Server treats XDCR's log file (goxdcr.log) like other log files, and encrypts it when you enable encryption for logs. |
There was a problem hiding this comment.
In line 99, this sentence is a bit confusing since it leaves me with a question -- so, are these encrypted? Also, the customers do not need to know that they are stored in an internal storage called "simple_store" since that can be changed at any time.
First sentence in line 99:
XDCR checkpoints, collection manifests, and broken maps use a separate storage mechanism (simple_store).
We should just say:
XDCR checkpoints, collection manifests, and broken maps are stored in a separate internal storage mechanism, and they are encrypted as well.
hyunjuV
left a comment
There was a problem hiding this comment.
I had one minor comment about the first sentence in line 99 in native-encryption-at-rest-overview.adoc.
Otherwise, lgtm.
I went ahead and approved (trust that any needed changes will be made).
DOC-14349
Preview1
Preview2