AWS bedrock-agentcore documentation change
Summary
Added documentation about using both InvokeAgentRuntime and InvokeAgentRuntimeCommand within the same session, clarifying that commands share the same container, filesystem, and environment as the agent, and updated session state description to include command execution.
Security assessment
The changes clarify operational behavior of runtime sessions and command execution but do not address any specific security vulnerability or weakness. No security fixes, vulnerabilities, or incidents are mentioned.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-sessions.md b/bedrock-agentcore/latest/devguide/runtime-sessions.md index d11582b26..00745cdeb 100644 --- a//bedrock-agentcore/latest/devguide/runtime-sessions.md +++ b//bedrock-agentcore/latest/devguide/runtime-sessions.md @@ -34 +34 @@ For data that needs to be retained beyond the session lifetime (such as user con -Unlike traditional serverless functions that terminate after each request, AgentCore supports ephemeral, isolated compute sessions lasting up to 8 hours. This simplifies building multi-step agentic workflows as you can make multiple calls to the same environment, with each invocation building upon the context established by previous interactions. +Unlike traditional serverless functions that terminate after each request, AgentCore supports ephemeral, isolated compute sessions lasting up to 8 hours. This simplifies building multi-step agentic workflows as you can make multiple calls to the same environment, with each invocation building upon the context established by previous interactions. You can use both `InvokeAgentRuntime` for agent reasoning and `InvokeAgentRuntimeCommand` for deterministic shell command execution within the same session. @@ -40 +40 @@ Unlike traditional serverless functions that terminate after each request, Agent -A new session is created on the first invoke with a unique runtimeSessionId provided by your application. AgentCore Runtime provisions a dedicated execution environment (microVM) for each session. Context is preserved between invocations to the same session. +A new session is created on the first invoke with a unique runtimeSessionId provided by your application. AgentCore Runtime provisions a dedicated execution environment (microVM) for each session. Context is preserved between invocations to the same session. Both `InvokeAgentRuntime` and `InvokeAgentRuntimeCommand` operate on the same session — a command sees the same container, filesystem, and environment as the agent. @@ -46 +46 @@ Sessions can be in one of the following states: - * **Active** : Either processing a sync request or doing background tasks. Sync invocation activity is automatically tracked based on invocations to a runtime session. Background tasks are communicated by the agent code by responding with "HealthyBusy" status in pings. + * **Active** : Either processing a sync request, executing a command, or doing background tasks. Sync invocation and command execution activity is automatically tracked based on invocations to a runtime session. Background tasks are communicated by the agent code by responding with "HealthyBusy" status in pings.