AWS bedrock-agentcore documentation change
Summary
Updated section headers and consolidated paragraphs about cross-region inference for AgentCore components, clarifying that data remains in primary region but prompts/results may move across regions within the same geography.
Security assessment
The changes are primarily formatting and clarification updates. The security-relevant statement about data transmission being encrypted across Amazon's secure network was already present and only received minor punctuation changes (straight apostrophe to curly apostrophe). No new security vulnerabilities or incidents are mentioned.
Diff
diff --git a/bedrock-agentcore/latest/devguide/cross-region-inference.md b/bedrock-agentcore/latest/devguide/cross-region-inference.md index 036b79dd2..15e7e6107 100644 --- a//bedrock-agentcore/latest/devguide/cross-region-inference.md +++ b//bedrock-agentcore/latest/devguide/cross-region-inference.md @@ -5 +5 @@ -Supported RegionsSupported Regions for Policy in AgentCoreSupported Regions for AgentCore Evaluations +Supported Regions for AgentCore Memory cross-region inferenceSupported Regions for Policy in AgentCore cross-region inferenceSupported Regions for AgentCore Evaluations cross-region inference @@ -11 +11 @@ With cross-region inference, Amazon Bedrock AgentCore Memory, Policy in AgentCor -For AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations, cross-region inference requests are kept within the AWS Regions that are part of the geography where the data originally resides. For example, a request made within the US is kept within the AWS Regions in the US. Although the data remains stored only in the primary region, when using cross-region inference, your input prompts and output results may move outside of your primary region. All data will be transmitted encrypted across Amazon's secure network. +For AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations, cross-region inference requests are kept within the AWS Regions that are part of the geography where the data originally resides. For example, a request made within the US is kept within the AWS Regions in the US. Although the data remains stored only in the primary region, when using cross-region inference, your input prompts and output results may move outside of your primary region. All data will be transmitted encrypted across Amazon’s secure network. @@ -15,7 +15 @@ For AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations, cross-regi -There's no additional cost for using cross-region inference. - -Amazon CloudWatch and AWS CloudTrail logs won't specify the AWS Region in which data inference occurs. - -For AgentCore Memory, if you don't want cross-region inference, you can manage your model selection using a [built-in with overrides strategy](./memory-custom-strategy.html). - -For AgentCore Evaluations, if you don't want cross-region inference, please see additional information on creating [custom evaluators](./custom-evaluators.html) that operate without CRIS. +There’s no additional cost for using cross-region inference. Amazon CloudWatch and AWS CloudTrail logs won’t specify the AWS Region in which data inference occurs. For AgentCore Memory, if you don’t want cross-region inference, you can manage your model selection using a [built-in with overrides strategy](./memory-custom-strategy.html) . For AgentCore Evaluations, if you don’t want cross-region inference, please see additional information on creating [custom evaluators](./custom-evaluators.html) that operate without CRIS.