AWS bedrock-agentcore documentation change
Summary
Updated documentation to replace references to 'AgentCore starter toolkit' with 'AgentCore CLI' in the context of creating a gateway service role.
Security assessment
The changes are purely about updating the tool name in the documentation. No security context or new security features are introduced.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md b/bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md index 1b3d8f18b..c71013ccd 100644 --- a//bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md +++ b//bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md @@ -28 +28 @@ If you prefer not to set up custom permissions, you can use the following option - * Use the AWS Management Console or AgentCore starter toolkit to create an AgentCore gateway service role with the proper permissions and gateway targets with the proper resource-based policies to allow the service role to access them. + * Use the AWS Management Console or AgentCore CLI to create an AgentCore gateway service role with the proper permissions and gateway targets with the proper resource-based policies to allow the service role to access them. @@ -113 +113 @@ When creating a gateway, you need a service role that has permissions to assume - * If you create a gateway in the AWS Management Console or through the AgentCore starter toolkit, you can choose to let AgentCore automatically create a service role for you with the necessary permissions. If you prefer this method, you can skip this prerequisite. + * If you create a gateway in the AWS Management Console or through the AgentCore CLI, you can choose to let AgentCore automatically create a service role for you with the necessary permissions. If you prefer this method, you can skip this prerequisite.