AWS bedrock-agentcore documentation change
Summary
Minor typographical change (straight apostrophe to curly apostrophe) in encryption documentation
Security assessment
Only a typographical change from 'don't' to 'don't' (with curly apostrophe). The documentation already discusses encryption for sensitive data, but this change doesn't add new security information or address any security vulnerability.
Diff
diff --git a/bedrock-agentcore/latest/devguide/storage-encryption.md b/bedrock-agentcore/latest/devguide/storage-encryption.md index 2ae8eed93..ca55e7e5a 100644 --- a//bedrock-agentcore/latest/devguide/storage-encryption.md +++ b//bedrock-agentcore/latest/devguide/storage-encryption.md @@ -7 +7 @@ -When creating an AgentCore Memory, it is important to make sure your data is safe and secure. If your application handles sensitive information (such as customer details, payment data, or personal chats), you must use encryption to protect this data. Consider using a customer-managed KMS key (CMK) for encryption. The service still encrypts data using a service managed key, even if you don't provide a CMK. Alternatively, you can also use an AWS-managed KMS key. In this case, you need to the add the following policy to the IAM user or role that you are using to setup memory. +When creating an AgentCore Memory, it is important to make sure your data is safe and secure. If your application handles sensitive information (such as customer details, payment data, or personal chats), you must use encryption to protect this data. Consider using a customer-managed KMS key (CMK) for encryption. The service still encrypts data using a service managed key, even if you don’t provide a CMK. Alternatively, you can also use an AWS-managed KMS key. In this case, you need to the add the following policy to the IAM user or role that you are using to setup memory.