You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/utilities/data_masking.md
+18-17
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,7 @@ Before you start, you will need a KMS symmetric key to encrypt and decrypt your
96
96
97
97
1. [Key policy examples using IAM Roles](https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-default.html#key-policy-default-allow-administrators){target="_blank"}
The following sequence diagrams explain how `DataMasking` behaves under different scenarios.
@@ -508,7 +509,7 @@ sequenceDiagram
508
509
509
510
#### Encrypt operation with multiple KMS Keys
510
511
511
-
When encrypting data with multiple KMS keys, the `aws_encryption_sdk`executes additional encryption calls to encrypt the data with each of the specified keys.
512
+
When encrypting data with multiple KMS keys, the `aws_encryption_sdk`makes additional API calls to encrypt the data with each of the specified keys.
512
513
513
514
<center>
514
515
```mermaid
@@ -520,19 +521,19 @@ sequenceDiagram
520
521
participant EncryptionProvider as Encryption Provider
521
522
Client->>Lambda: Invoke (event)
522
523
Lambda->>DataMasking: Init Encryption Provider with master key
523
-
Note over Lambda,DataMasking: AWSEncryptionSDKProvider([KMS_KEY])
524
+
Note over Lambda,DataMasking: AWSEncryptionSDKProvider([KEY_1, KEY_2])
524
525
Lambda->>DataMasking: encrypt(data)
525
526
DataMasking->>EncryptionProvider: Create unique data key
526
-
Note over DataMasking,EncryptionProvider: KMS GenerateDataKey API
527
+
Note over DataMasking,EncryptionProvider: KMS GenerateDataKey API - KEY_1
527
528
DataMasking->>DataMasking: Cache new unique data key
0 commit comments