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