AWS bedrock-agentcore documentation change
Summary
Removed 'Amazon Bedrock' from description of VPC condition keys (minor branding adjustment)
Security assessment
Change only adjusts product name reference without modifying security controls or policies. No evidence of security vulnerability being addressed.
Diff
diff --git a/bedrock-agentcore/latest/devguide/security-vpc-condition.md b/bedrock-agentcore/latest/devguide/security-vpc-condition.md index ae1a8cec1..f3d45d34c 100644 --- a//bedrock-agentcore/latest/devguide/security-vpc-condition.md +++ b//bedrock-agentcore/latest/devguide/security-vpc-condition.md @@ -9 +9 @@ Example policies with condition keys for VPC settings -You can use Amazon Bedrock AgentCore-specific condition keys for VPC settings to provide additional permission controls for your AgentCore Runtime and built-in tools. For example, you can require that all runtimes in your organization are connected to a VPC. You can also specify the subnets and security groups that users of the AgentCore Runtime can and can't use. +You can use AgentCore-specific condition keys for VPC settings to provide additional permission controls for your AgentCore Runtime and built-in tools. For example, you can require that all runtimes in your organization are connected to a VPC. You can also specify the subnets and security groups that users of the AgentCore Runtime can and can't use.