New Relic and AWS Give AI Coders Production Vision with Kiro Integration
- 94% of engineering leaders rate AI-generated code highly, but 78% have seen an increase in production incidents.
- 82% of engineering leaders have experienced outright failures tied to AI-generated code.
- One-click integration embeds New Relic's real-time observability into Kiro's AI workflows.
Experts would likely conclude that this integration addresses critical gaps in AI-driven development by providing real-time production context, enhancing both speed and reliability in software delivery.
New Relic and AWS Give AI Coders Production Vision with Kiro Integration
NEW YORK, NY – June 17, 2026 – In a move set to redefine how artificial intelligence builds software, New Relic today announced a deep integration with Kiro, Amazon Web Services' agentic development environment. Unveiled at the AWS Summit NYC, the one-click integration embeds New Relic's real-time observability data directly into Kiro's AI-driven workflows, effectively giving AI coding agents the production context they have critically lacked.
The partnership aims to bridge the treacherous gap between AI-generated code and production-ready applications. By feeding live metrics, logs, and traces into Kiro via its Model Context Protocol (MCP) Server, New Relic is allowing developers to validate AI-generated code against live operational realities without ever leaving their development environment. For enterprises racing to deploy AI, this promises to accelerate development while mitigating the significant risks of shipping code written by agents that are, until now, flying blind.
Closing the AI-Ops Feedback Loop
The rise of agentic coding—where AI agents handle complex, multi-step development tasks—has been a double-edged sword. While promising unprecedented developer velocity, it has also introduced new failure modes. A recent industry survey highlighted this tension, revealing that while 94% of engineering leaders rate AI-generated code highly, 78% have seen an increase in production incidents and 82% have experienced outright failures tied to its use. The core problem is context: AI agents can write code, but they lack awareness of the live environment where that code will run.
This is the problem the New Relic-Kiro integration is built to solve. Kiro, which AWS launched in mid-2025, was designed to impose engineering discipline on AI development through a methodology called “spec-driven development.” Instead of just generating code from a vague prompt, Kiro first translates requirements into a detailed technical specification, breaks the work into atomic tasks, and then generates code. This structured approach is designed to create maintainable, scalable software.
Now, New Relic’s integration injects the final, crucial ingredient: production reality. Developers using Kiro can now query their entire technology stack in natural language. An engineer can ask, “What was the p99 latency for the checkout service over the last hour?” or “Show me error logs related to the new inventory API,” and receive an immediate answer from New Relic’s platform directly within their IDE. This closes the feedback loop between planning, coding, and validation, ensuring AI-generated changes are operationally sound before they ever reach production.
“As organizations navigate this agentic transformation, they face a critical and immediate need to safely unify AI coding agents and live business data,” said New Relic Chief Product Officer Brian Emerson. “By integrating our MCP Server with Kiro, we are combining the rigorous, spec-driven development on AWS with New Relic’s deep operational insights. The result is a seamless, one-click solution that empowers developer teams to confidently ship quality code with minimal operational friction and toil.”
From Reactive Firefighting to Intelligent Orchestration
For developers and Site Reliability Engineers (SREs), the practical impact is a shift from manual, context-switching-heavy troubleshooting to AI-assisted investigation. When a performance bottleneck is detected, Kiro’s agents, now armed with New Relic’s telemetry, can help pinpoint the root cause and even suggest a precise code fix. This promises a dramatic reduction in Mean Time To Resolution (MTTR), a key metric for operational excellence.
The integration is delivered as a “Kiro power,” a one-click add-on that eliminates complex configuration. This ease of deployment is central to the strategy, enabling engineering teams to immediately access observability insights and accelerate their transition to a more mature, AI-native development model. It standardizes how AI agents access vital data, leveraging the open Model Context Protocol to avoid the “integration sprawl” that plagues many enterprise AI initiatives.
Beyond the developer’s desktop, this move has profound implications for business strategy. For Chief Technology Officers and business leaders, the integration represents a significant de-risking of their AI investments. By building a safety layer of observability around AI-driven development, it enables organizations to harness the speed of agentic coding without sacrificing the quality and reliability essential for protecting revenue and customer experience. This moves the entire software lifecycle closer to a state of “intelligent orchestration,” where AI not only writes code but also helps manage, monitor, and optimize it in a continuous, automated loop.
A Deepening Alliance on the AI Frontier
Today’s announcement is not an isolated event but the latest chapter in a long-standing and deepening strategic collaboration between New Relic and AWS. The partnership, which was formalized with a Strategic Collaboration Agreement in 2020, has steadily evolved from foundational cloud migration and monitoring to the cutting edge of AI-driven operations. Just this past April, New Relic announced it had surpassed $1 billion in lifetime transactions through the AWS Marketplace, a milestone reflecting deep customer trust and the success of their joint go-to-market efforts.
This Kiro integration builds on prior technical collaborations, including the integration of New Relic's MCP Server with the AWS DevOps Agent, which gave that tool similar powers of root cause analysis. The consistent strategy is to embed New Relic's intelligence wherever engineering work is happening within the AWS ecosystem. As one industry analyst noted, “Observability is the bedrock of trustworthy AI. Without it, agentic systems are a black box. The tight coupling of New Relic and AWS native tools is creating a powerful, defensible position in the enterprise AI market.”
The shared vision is clear: to create an ecosystem where AI-powered development is not only fast but also safe, reliable, and intrinsically linked to business outcomes. As agentic AI moves from the experimental phase to a core component of enterprise software delivery, the alliance between New Relic’s observability intelligence and AWS’s cloud and AI infrastructure positions both companies to lead the charge in this new frontier.
📝 This article is still being updated
Are you a relevant expert who could contribute your opinion or insights to this article? We'd love to hear from you. We will give you full credit for your contribution.
Contribute Your Expertise →