New Relic integrates Kiro as AWS sales top USD $1 billion

New Relic has integrated its Model Context Protocol Server with AWS's Kiro development environment. The move comes as New Relic passes USD $1 billion in lifetime AWS Marketplace transactions.

The integration is intended to bring production observability data into the development environment, allowing engineers to query live metrics, events, logs, and traces in natural language while working inside Kiro. It gives development teams a way to check how code performs against production conditions before software is released.

Agentic coding tools are becoming more common as companies adopt AI-assisted development, but concerns remain about how those tools operate without direct production context. New Relic's product is designed to connect that operational data to Kiro's spec-driven workflow so developers, DevOps teams, and Site Reliability Engineers can work from the same information.

The integration can be deployed with one click inside Kiro, removing the need for manual setup. The aim is to make observability data available within the integrated development environment rather than through separate monitoring tools.

Development workflow

The setup allows teams to surface production context during software planning and validation. By bringing full-stack telemetry into Kiro, developers can test whether AI-generated code changes meet technical requirements and operational expectations before release.

It also supports AI-assisted investigation of performance problems by feeding observability data to Kiro's agents. This gives engineers a way to identify the source of issues and apply code changes without moving between multiple systems.

"As organizations navigate this agentic transformation, they face a critical and immediate need to safely unify AI coding agents and live business data," said Brian Emerson, Chief Product Officer, New Relic.

"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," Emerson said.

AWS milestone

The launch also marks a commercial milestone in New Relic's relationship with AWS. It has now surpassed USD $1 billion in lifetime transactions through AWS Marketplace, reflecting the scale of customer purchasing through the cloud provider's marketplace channel.

The figure underscores the importance of AWS as a route to market for software vendors selling monitoring, observability, and related developer tools. It also points to sustained enterprise demand for New Relic's products among customers already standardising procurement through cloud platforms.

New Relic positioned the Kiro integration as part of a broader shift in its AWS partnership, from infrastructure monitoring toward observability products tied more closely to AI-driven development and automated remediation. It cited recent technical links, including its MCP Server integration for AWS DevOps Agent and remediation workflows using AWS AppConfig.

Operational focus

The Kiro integration addresses a central gap between code generation and production behaviour. AI coding tools can help teams write and modify software more quickly, but software leaders are under pressure to show that AI-produced code can be monitored, checked, and corrected before it creates performance or reliability problems in live systems.

For development teams, the practical appeal lies in being able to ask for production information in natural language inside the coding environment. Instead of leaving the IDE to inspect dashboards or monitoring systems separately, engineers can work with operational data in the same workflow as specification writing and code generation.

This may also matter for companies facing tighter internal controls over AI use in software delivery. Governance teams and Chief Information Officers are increasingly asking how automated development tools are validated, what evidence exists before deployment, and how quickly faults can be traced once software reaches production.

The integration is available through the Kiro product page as an add-on within the environment. The objective is to give engineering teams immediate access to observability data at the point where code decisions are made.

The latest move links New Relic's observability tools more directly to the growing use of AI-native development environments, as software companies compete to place operational data closer to the code-writing process.