AWS bedrock-agentcore documentation change

Service: bedrock-agentcore · 2026-04-19 · Documentation low

File: bedrock-agentcore/latest/devguide/gateway-vpc-egress.md

Summary

Changed field name from 'managedLatticeResource' to 'managedVpcResource' in multiple example configurations

Security assessment

This appears to be a routine API field name update in documentation examples. There's no indication this change addresses a security vulnerability; it's likely a terminology or API update. The change relates to VPC egress configuration but doesn't show evidence of fixing a security issue.

Diff

diff --git a/bedrock-agentcore/latest/devguide/gateway-vpc-egress.md b/bedrock-agentcore/latest/devguide/gateway-vpc-egress.md
index 9f1f81980..f4ba08256 100644
--- a//bedrock-agentcore/latest/devguide/gateway-vpc-egress.md
+++ b//bedrock-agentcore/latest/devguide/gateway-vpc-egress.md
@@ -33 +33 @@ The following example creates a private MCP server target using managed Lattice:
-        "managedLatticeResource": {
+        "managedVpcResource": {
@@ -143 +143 @@ The following example creates a private OpenAPI target using managed Lattice:
-        "managedLatticeResource": {
+        "managedVpcResource": {
@@ -259 +259 @@ API Gateway targets with private endpoints are not natively supported. However,
-        "managedLatticeResource": {
+        "managedVpcResource": {