AWS bedrock-agentcore documentation change
Summary
Updated terminology from 'AgentCore Policy' to 'Policy in AgentCore' throughout document. Changed section headers and regional references to match new naming convention.
Security assessment
The changes appear to be terminology updates rather than addressing security vulnerabilities. The existing security statements about encrypted data transmission remain unchanged.
Diff
diff --git a/bedrock-agentcore/latest/devguide/cross-region-inference.md b/bedrock-agentcore/latest/devguide/cross-region-inference.md index caacadfd3..20767e683 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 AgentCore PolicySupported Regions for AgentCore Evaluations +Supported RegionsSupported Regions for Policy in AgentCoreSupported Regions for AgentCore Evaluations @@ -7 +7 @@ Supported RegionsSupported Regions for AgentCore PolicySupported Regions for Age -# Cross-region inference in Amazon Bedrock AgentCore Memory, Amazon Bedrock AgentCore Policy, and AgentCore Evaluations +# Cross-region inference in Amazon Bedrock AgentCore Memory, Policy in Amazon Bedrock AgentCore, and AgentCore Evaluations @@ -9 +9 @@ Supported RegionsSupported Regions for AgentCore PolicySupported Regions for Age -With cross-region inference, Amazon Bedrock AgentCore Memory, AgentCore Policy, and AgentCore Evaluations will automatically select the optimal region within your geography (as described in more detail below) to process your inference request, maximizing available compute resources and model availability, and providing the best customer experience. +With cross-region inference, Amazon Bedrock AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations will automatically select the optimal region within your geography (as described in more detail below) to process your inference request, maximizing available compute resources and model availability, and providing the best customer experience. @@ -11 +11 @@ With cross-region inference, Amazon Bedrock AgentCore Memory, AgentCore Policy, -For AgentCore Memory, AgentCore Policy, 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. @@ -27 +27 @@ For AgentCore Evaluations, if you don't want cross-region inference, please see - * Supported Regions for AgentCore Policy cross-region inference + * Supported Regions for Policy in AgentCore cross-region inference @@ -44 +44 @@ Asia Pacific | Asia Pacific (Tokyo) (ap-northeast-1) Asia Pacific (Mumbai) (ap- -## Supported Regions for AgentCore Policy cross-region inference +## Supported Regions for Policy in AgentCore cross-region inference @@ -48 +48 @@ For a list of Region codes and endpoints supported in AgentCore, see [Supported -Supported AgentCore Policy geography | Inference regions +Supported Policy in AgentCore geography | Inference regions