AWS bedrock-agentcore documentation change
Summary
Updated terminology from 'managedVpcResource' to 'managedLatticeResource' throughout the documentation for creating and managing private endpoints
Security assessment
This change appears to be a terminology update or API parameter name change from 'managedVpcResource' to 'managedLatticeResource'. While it relates to VPC egress and private endpoints (which are security features), there's no evidence this addresses a specific security vulnerability or weakness. It's likely a documentation correction or API update.
Diff
diff --git a/bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md b/bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md index d6f99ffd2..cb46cf02e 100644 --- a//bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md +++ b//bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md @@ -136 +136 @@ Before creating a gateway target with a managed private endpoint, ensure the fol -To create a resource with a managed private endpoint, include the `privateEndpoint.managedVpcResource` block in your create request. +To create a resource with a managed private endpoint, include the `privateEndpoint.managedLatticeResource` block in your create request. @@ -142 +142 @@ To create a resource with a managed private endpoint, include the `privateEndpoi - "managedVpcResource": { + "managedLatticeResource": { @@ -152 +152 @@ To create a resource with a managed private endpoint, include the `privateEndpoi -The `managedVpcResource` block accepts the following fields: +The `managedLatticeResource` block accepts the following fields: @@ -193 +193 @@ After the resource is created, call the relevant Get API (for example, `GetGatew - "managedVpcResource": { + "managedLatticeResource": { @@ -369 +369 @@ The following example shows how to create a gateway target for a private API Gat - "managedVpcResource": { + "managedLatticeResource": { @@ -387 +387 @@ The following example shows how to create a gateway target for a private API Gat -The `routingDomain` field is only available for the `managedVpcResource` option. For self-managed Lattice, configure the routing domain directly in your resource configuration when you create it. +The `routingDomain` field is only available for the `managedLatticeResource` option. For self-managed Lattice, configure the routing domain directly in your resource configuration when you create it. @@ -465 +465 @@ Use the ALB DNS name as the `routingDomain` and the public cert domain as the ta - "managedVpcResource": { + "managedLatticeResource": { @@ -479 +479 @@ The target URL in your target configuration should use `https://my-server.my-com -When you create a gateway target with a managed private endpoint ( `managedVpcResource` ), AgentCore uses the `AWSServiceRoleForBedrockAgentCoreGatewayNetwork` service-linked role to create and manage VPC Lattice resource gateways in your account. This role is created automatically the first time you create a managed private endpoint target, provided your IAM principal has the required `iam:CreateServiceLinkedRole` permission. +When you create a gateway target with a managed private endpoint ( `managedLatticeResource` ), AgentCore uses the `AWSServiceRoleForBedrockAgentCoreGatewayNetwork` service-linked role to create and manage VPC Lattice resource gateways in your account. This role is created automatically the first time you create a managed private endpoint target, provided your IAM principal has the required `iam:CreateServiceLinkedRole` permission.