Skip to content

Commit c26bf4b

Browse files
Update changes/2025-06-30_branch_keys_version_2/un-modeled_branch_key_context_key_values.md
Co-authored-by: Tony Knapp <[email protected]>
1 parent 966b22c commit c26bf4b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

changes/2025-06-30_branch_keys_version_2/un-modeled_branch_key_context_key_values.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ See [background](./background.md) for an introduction to Hierarchy Version 2 (HV
1111

1212
The issue at hand is what to do about un-prefixed context of a Branch Key.
1313

14-
These are any members of the Branch Key's Context whose key is not prefixed by `aws-crypto-ec:` OR another reserved Branch Key Context Key Name, such as `kms-arn` or `hierarchy-version`.
14+
These are any members of the Branch Key's Context whose key is not prefixed by `aws-crypto-ec:` OR not another reserved Branch Key Context Key Name, such as `kms-arn` or `hierarchy-version`.
1515
Such Key-Value pairs were NOT added to a Branch Key Item by a Crypto Tools product.
1616
But they could have been added by an AWS Cryptographic Material Providers Library (MPL) Consumer manually.
1717
As long as this is done properly, the AWS KMS Hierarchical Keyring will use these manually modified Branch Keys.

0 commit comments

Comments
 (0)