AWS bedrock-agentcore documentation change
Summary
Added new section 'Session headers by protocol' that lists the specific session headers for different protocols (MCP, HTTP, A2A, AGUI) and explains microVM stickiness for routing requests to the same microVM instance.
Security assessment
The change provides documentation about session headers for different protocols to maintain session affinity and avoid cold start latency. No security vulnerabilities, encryption, access control, or security features are discussed. This is purely about performance and routing behavior.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-sessions.md b/bedrock-agentcore/latest/devguide/runtime-sessions.md index 85cd01a82..90814baf2 100644 --- a//bedrock-agentcore/latest/devguide/runtime-sessions.md +++ b//bedrock-agentcore/latest/devguide/runtime-sessions.md @@ -5 +5 @@ -Understanding ephemeral contextExtended conversations and multi-step workflowsAgentCore Runtime session lifecycleHow to use sessions +Understanding ephemeral contextExtended conversations and multi-step workflowsAgentCore Runtime session lifecycleHow to use sessionsSession headers by protocol @@ -91,0 +92,15 @@ By using the same runtimeSessionId for related invocations, you ensure that cont +## Session headers by protocol + +When invoking agents, include the appropriate session header to ensure requests are routed to the same microVM. The header depends on your agent's configured protocol: + +Session headers by protocol Protocol | Session Header +---|--- +MCP | `Mcp-Session-Id` +HTTP | `X-Amzn-Bedrock-AgentCore-Runtime-Session-Id` +A2A | `X-Amzn-Bedrock-AgentCore-Runtime-Session-Id` +AGUI | `X-Amzn-Bedrock-AgentCore-Runtime-Session-Id` + +**MicroVM stickiness** : Amazon Bedrock AgentCore uses the session header to route requests to the same microVM instance. Clients must capture the session ID returned in the response and include it in all subsequent requests to ensure session affinity. Without a consistent session ID, each request may be routed to a new microVM, which may result in additional latency due to cold starts. + +For MCP protocol specifics including stateless and stateful modes, see [MCP session management and microVM stickiness](./runtime-mcp-protocol-contract.html#mcp-session-management). +