AWS says DevOps Agent now supports custom SRE agents, bring-your-own sub-agents, and headless access through MCP and A2A remote servers, extending how teams can investigate production health, logs, anomalies, and database reports from developer tools.
AWS has expanded DevOps Agent with support for custom SRE agents, bring-your-own sub-agents, and headless access through MCP and A2A protocols, according to an AWS “What’s New” announcement.
In its announcement, AWS says the updated DevOps Agent can help developers investigate production health, logs, anomalies, and database reports from tools such as Kiro and Claude. The company describes the change as an expansion of how DevOps Agent can be accessed and customized, rather than only as a standalone experience.
AWS Documentation separately describes dedicated DevOps Agent remote servers for MCP and A2A. According to the documentation, these remote servers provide endpoints, supported protocols, authentication details, and client integration guidance for connecting external tools to DevOps Agent.
The practical effect is that teams can use DevOps Agent capabilities from other development environments, provided those clients support the relevant protocol and authentication setup described by AWS.
AWS Documentation also explains how to create a custom agent in DevOps Agent. The documented setup includes configuring system prompts, assigning MCP tools, and attaching skills inside an Agent Space.
That customization matters for site reliability engineering workflows because SRE investigations often depend on organization-specific runbooks, observability tools, and operational practices. AWS says DevOps Agent now supports custom SRE agents and bring-your-own sub-agents, which suggests teams can shape assistant behavior around particular operational responsibilities.
AWS’s documentation indicates that custom agents can be given specific instructions and tool access. Those controls are important because production debugging usually requires more than generic chat: an assistant may need access to logs, metrics, anomaly findings, or database-related reports, while still operating within the permissions and tools configured by the organization.
The AWS Documentation page on connecting to DevOps Agent remote servers lists MCP and A2A as supported approaches for remote access. MCP, commonly used to connect AI assistants with tools and data sources, can allow a compatible client to call available tools exposed by a service. A2A is presented by AWS as another supported protocol for interacting with DevOps Agent remote servers.
AWS says this enables “headless” access, meaning DevOps Agent can be used without relying only on a built-in graphical interface. Instead, developers can interact with it from supported clients such as Kiro and Claude, as named in the AWS announcement.
For engineering teams, this could reduce context switching during incident review or operational troubleshooting. A developer working in a preferred AI-enabled environment may be able to ask about application health or investigate logs without moving into a separate console, depending on the tools and permissions configured.
The sources do not provide benchmark data or independent reliability assessments, so teams should treat the release as a capability expansion rather than evidence of improved incident outcomes.
Before adopting the new options, organizations should review AWS’s authentication guidance for DevOps Agent remote servers and decide which clients are appropriate for production-related access. They should also examine how custom agents are configured, what MCP tools are assigned, and which skills are attached in an Agent Space.
The most important implementation questions are likely to be operational and security-related: who can invoke a DevOps Agent remote server, what systems it can query, what actions its tools can perform, and how its responses are reviewed during production incidents.
AWS’s announcement and documentation show that DevOps Agent is becoming more extensible and easier to reach from external developer tools. The value for customers will depend on how carefully they configure custom agents, protocol access, and permissions around real SRE workflows.
AWS has expanded DevOps Agent with support for custom SRE agents, bring your own sub agents, and headless access through MCP and A2A protocols, according to an AWS “What’s New” announcement.
What AWS announced In its announcement, AWS says the updated DevOps Agent can help developers investigate production health, logs, anomalies, and database reports from tools such as Kiro and Claude.
The company describes the change as an expansion of how DevOps Agent can be accessed and customized, rather than only as a standalone experience.
Continue reading
