AWS bedrock-agentcore documentation change
Summary
Updated multiple references from 'managedLatticeResource' to 'managedVpcResource' in the VPC egress private endpoints documentation, including configuration blocks and field descriptions
Security assessment
This change consistently updates the configuration parameter name from 'managedLatticeResource' to 'managedVpcResource' throughout the VPC egress private endpoints documentation. The change includes updates to code examples, field descriptions, and service-linked role references. This is a terminology/branding update without any security implications. The documentation continues to describe the same security feature (managed private endpoints) but with updated parameter names.
Diff
diff --git a/bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md b/bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md index cb46cf02e..d6f99ffd2 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.managedLatticeResource` block in your create request. +To create a resource with a managed private endpoint, include the `privateEndpoint.managedVpcResource` block in your create request. @@ -142 +142 @@ To create a resource with a managed private endpoint, include the `privateEndpoi - "managedLatticeResource": { + "managedVpcResource": { @@ -152 +152 @@ To create a resource with a managed private endpoint, include the `privateEndpoi -The `managedLatticeResource` block accepts the following fields: +The `managedVpcResource` block accepts the following fields: @@ -193 +193 @@ After the resource is created, call the relevant Get API (for example, `GetGatew - "managedLatticeResource": { + "managedVpcResource": { @@ -369 +369 @@ The following example shows how to create a gateway target for a private API Gat - "managedLatticeResource": { + "managedVpcResource": { @@ -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 `managedLatticeResource` 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 `managedVpcResource` 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 - "managedLatticeResource": { + "managedVpcResource": { @@ -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 ( `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. +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.