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: changes/2025-06-30_branch_keys_version_2/background.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -248,9 +248,6 @@ i.e: They need to update their readers before they update their writers.
248
248
This alone is justification for the policy.
249
249
250
250
**Consistent KMS Encryption Context**:
251
-
[Much has been said for](https://quip-amazon.com/rc9CARWxsCTT#LHG9AA64tJh) and [against the Encryption Context](https://quip-amazon.com/l5d8AHH0hgZs/Encryption-Context-Exposure-by-Dynamo-ESDK)
252
-
witnessed by KMS in HV-1.
253
-
254
251
The arguments for the HV-1 Encryption Context suggest
255
252
users SHOULD be able to restrict their Branch Key Store clients
256
253
to a HV-1 such that they know any IAM or KMS Key Policies
0 commit comments