@@ -113,7 +113,11 @@ StrictAwsKmsMasterKeyProvider
113
113
A ``StrictAwsKmsMasterKeyProvider `` is configured with an explicit list of AWS KMS
114
114
CMKs with which to encrypt and decrypt data. On encryption, it encrypts the plaintext with all
115
115
configured CMKs. On decryption, it only attempts to decrypt ciphertexts that have been wrapped
116
- with one of the configured CMKs.
116
+ with a CMK that matches one of the configured CMK ARNs.
117
+
118
+ To create a ``StrictAwsKmsMasterKeyProvider `` you must provide one or more CMKs. For providers that will only
119
+ be used for encryption, you can use any valid `KMS key identifier `_. For providers that will be used for decryption, you
120
+ must use the key ARN; key ids, alias names, and alias ARNs are not supported.
117
121
118
122
Because the ``StrictAwsKmsMasterKeyProvider `` uses the `boto3 SDK `_ to interact with `AWS KMS `_,
119
123
it requires AWS Credentials.
@@ -122,10 +126,6 @@ pre-existing instance of a ``botocore session`` to the ``StrictAwsKmsMasterKeyPr
122
126
This latter option can be useful if you have an alternate way to store your AWS credentials or
123
127
you want to reuse an existing instance of a botocore session in order to decrease startup costs.
124
128
125
- To create a ``StrictAwsKmsMasterKeyProvider `` you must provide one or more CMKs. For providers that will only
126
- be used for encryption, you can use any valid `KMS key identifier `_. For providers that will be used for decryption, you
127
- must use the key ARN; key ids, alias names, and alias ARNs are not supported.
128
-
129
129
If you configure the the ``StrictAwsKmsMasterKeyProvider `` with multiple CMKs, the `final message `_
130
130
will include a copy of the data key encrypted by each configured CMK.
131
131
0 commit comments