AWS bedrock-agentcore documentation change
Summary
Removed preview notice, updated port/path formatting with backticks, added API reference link, and minor wording improvements
Security assessment
Changes focus on documentation clarity (formatting ports/paths) and API reference linking. No security vulnerabilities addressed or new security features documented. Existing mentions of authentication (SigV4/OAuth 2.0) remain unchanged.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-a2a.md b/bedrock-agentcore/latest/devguide/runtime-a2a.md index 1366dcfcf..e1e6070ec 100644 --- a//bedrock-agentcore/latest/devguide/runtime-a2a.md +++ b//bedrock-agentcore/latest/devguide/runtime-a2a.md @@ -7,2 +6,0 @@ How Amazon Bedrock AgentCore supports A2AUsing A2A with AgentCore RuntimeAppendi -Amazon Bedrock AgentCore is in preview release and is subject to change. - @@ -43 +41 @@ In this section, you learn: -Amazon Bedrock AgentCore's A2A protocol support enables seamless integration with A2A servers by acting as a transparent proxy layer. When configured for A2A, Amazon Bedrock AgentCore expects containers to run stateless, streamable HTTP servers on port 9000 at the root path (0.0.0.0:9000/), which aligns perfectly with default A2A server configuration. +Amazon Bedrock AgentCore's A2A protocol support enables seamless integration with A2A servers by acting as a transparent proxy layer. When configured for A2A, Amazon Bedrock AgentCore expects containers to run stateless, streamable HTTP servers on port `9000` at the root path (`0.0.0.0:9000/`), which aligns with the default A2A server configuration. @@ -45 +43 @@ Amazon Bedrock AgentCore's A2A protocol support enables seamless integration wit -The service provides enterprise-grade session isolation while maintaining protocol transparency - JSON-RPC payloads from the `InvokeAgentRuntime` API are passed through directly to the A2A container without modification. This architecture preserves the standard A2A protocol features like built-in agent discovery through Agent Cards at /.well-known/agent-card.json and JSON-RPC communication, while adding enterprise authentication (SigV4/OAuth 2.0) and scalability. +The service provides enterprise-grade session isolation while maintaining protocol transparency - JSON-RPC payloads from the [InvokeAgentRuntime](https://docs.aws.amazon.com/bedrock-agentcore/latest/APIReference/API_InvokeAgentRuntime.html) API are passed through directly to the A2A container without modification. This architecture preserves the standard A2A protocol features like built-in agent discovery through Agent Cards at `/.well-known/agent-card.json` and JSON-RPC communication, while adding enterprise authentication (SigV4/OAuth 2.0) and scalability. @@ -47 +45 @@ The service provides enterprise-grade session isolation while maintaining protoc -The key differentiators from other protocols are the port (9000 vs 8080 for HTTP), mount path (/ vs /invocations), and the standardized agent discovery mechanism, making Amazon Bedrock AgentCore an ideal deployment platform for A2A agents in production environments. +The key differentiators from other protocols are the port (9000 vs 8080 for HTTP), mount path (`/` vs `/invocations`), and the standardized agent discovery mechanism, making Amazon Bedrock AgentCore an ideal deployment platform for A2A agents in production environments.