AWS bedrock documentation change
Summary
Fixed a double slash in the URL for the Hierarchical Keyring documentation link.
Security assessment
The change corrects a URL formatting issue but does not alter the security content or address a specific security vulnerability. The encryption context and key management practices described remain unchanged.
Diff
diff --git a/bedrock/latest/userguide/ltm-permissions.md b/bedrock/latest/userguide/ltm-permissions.md index 4416818a3..987032e4f 100644 --- a//bedrock/latest/userguide/ltm-permissions.md +++ b//bedrock/latest/userguide/ltm-permissions.md @@ -11 +11 @@ If you've enabled memory for your agent and if you encrypt agent sessions with a -Amazon Bedrock uses these permissions to generate encrypted data keys and then use the generated keys to encrypt agent memory. Amazon Bedrock also needs permissions to re-encrypt the the generated data key with different encryption contexts. Re-encrypt permissions are also used when customer managed key transitions between another customer managed key or service owned key. For more information, see [Hierarchical Keyring](https://docs.aws.amazon.com/database-encryption-sdk/latest/devguide/use-hierarchical-keyring.html). +Amazon Bedrock uses these permissions to generate encrypted data keys and then use the generated keys to encrypt agent memory. Amazon Bedrock also needs permissions to re-encrypt the the generated data key with different encryption contexts. Re-encrypt permissions are also used when customer managed key transitions between another customer managed key or service owned key. For more information, see [Hierarchical Keyring](https://docs.aws.amazon.com//database-encryption-sdk/latest/devguide/use-hierarchical-keyring.html).