AWS bedrock-agentcore documentation change
Summary
Changed apostrophe in 'don't' to curly quote for consistency in data protection advice.
Security assessment
Minor punctuation update from straight to curly apostrophe; no change to the security guidance about avoiding sensitive data in free-form fields or URLs. No indication of fixing a security issue or adding new security documentation.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-data-protection.md b/bedrock-agentcore/latest/devguide/identity-data-protection.md index bc9b9c04a..4f0b4ba21 100644 --- a//bedrock-agentcore/latest/devguide/identity-data-protection.md +++ b//bedrock-agentcore/latest/devguide/identity-data-protection.md @@ -24 +24 @@ For data protection purposes, we recommend that you protect AWS account credenti -We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a **Name** field. This includes when you work with Amazon Bedrock AgentCore Identity or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Amazon Bedrock AgentCore Identity or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server. +We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a **Name** field. This includes when you work with Amazon Bedrock AgentCore Identity or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Amazon Bedrock AgentCore Identity or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don’t include credentials information in the URL to validate your request to that server.