Skip to content

DOCSP-15532 fix 4.4.5 merge conflicts with NextGen #5183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 8, 2021
Merged

DOCSP-15532 fix 4.4.5 merge conflicts with NextGen #5183

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions source/core/security-client-side-encryption-key-management.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,8 +71,7 @@ Key must have at least one policy with the following actions:
`(reference)
<https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html>`__

.. admonition:: Implement Principle of Least Privilege for KMS Access
:class: note
.. note:: Implement Principle of Least Privilege for KMS Access

Consider configuring IAM user roles such that MongoDB has only the
access to the actions and resources required to function.
Expand Down Expand Up @@ -210,29 +209,30 @@ The :binary:`~bin.mongo` shell provides helper methods for data
encryption key management:

.. list-table::
:widths: 40 40
:header-rows: 1
:widths: 60 40

* - Use Case
- Helper Methods

* - Retrieving data encryption keys
-
- :method:`KeyVault.getKey()`
- :method:`KeyVault.getKeys()`
- :method:`KeyVault.getKeyByAltName()`
- | :method:`KeyVault.getKey()`
| :method:`KeyVault.getKeys()`
| :method:`KeyVault.getKeyByAltName()`

* - Creating or Modifying data encryption keys
-
- :method:`KeyVault.createKey()`
- :method:`KeyVault.addKeyAlternateName()`
- :method:`KeyVault.removeKeyAlternateName()`
- | :method:`KeyVault.createKey()`
| :method:`KeyVault.addKeyAlternateName()`
| :method:`KeyVault.removeKeyAlternateName()`

* - Removing data encryption keys

- :method:`KeyVault.deleteKey()`

.. important::

Removing a data encryption key renders all fields encrypted
using that data encryption key as permanently unreadable.

-
- :method:`KeyVault.deleteKey()`

Applications with :authrole:`read` access to the key vault collection
can retrieve data encryption keys by querying the collection. However,
Expand All @@ -245,7 +245,7 @@ vault. Applications must have access to both the remote key vault
cluster and the connection cluster to perform client-side field level
encryption operations.

data encryption keys have the following structure:
Data encryption keys have the following structure:

.. code-block:: json

Expand Down