AWS bedrock-agentcore documentation change
Summary
Updated terminology in service-linked role documentation by replacing 'managedVpcResource' with 'managedLatticeResource' in three places for gateway target configuration.
Security assessment
This change updates configuration parameter names in service-linked role documentation. It appears to be a terminology alignment with no security implications or evidence of addressing security vulnerabilities.
Diff
diff --git a/bedrock-agentcore/latest/devguide/service-linked-roles.md b/bedrock-agentcore/latest/devguide/service-linked-roles.md index d7e1570aa..22038b509 100644 --- a//bedrock-agentcore/latest/devguide/service-linked-roles.md +++ b//bedrock-agentcore/latest/devguide/service-linked-roles.md @@ -326 +326 @@ When you create a gateway target with a managed private endpoint: - 1. You specify the VPC, subnets, and optional security groups for the private endpoint in the `managedVpcResource` configuration + 1. You specify the VPC, subnets, and optional security groups for the private endpoint in the `managedLatticeResource` configuration @@ -351 +351 @@ You don’t need to manually create service-linked roles. AgentCore creates them - * **Gateway service-linked role** : Created when you create a AgentCore Gateway target with a managed private endpoint ( `managedVpcResource` ) configuration + * **Gateway service-linked role** : Created when you create a AgentCore Gateway target with a managed private endpoint ( `managedLatticeResource` ) configuration @@ -419 +419 @@ If you no longer need to use a feature or service that requires a service-linked - * **Gateway service-linked role** : Delete all AgentCore Gateway targets that use managed private endpoints ( `managedVpcResource` configuration) + * **Gateway service-linked role** : Delete all AgentCore Gateway targets that use managed private endpoints ( `managedLatticeResource` configuration)