What's New

Amazon Quick, AWS's AI assistant for workplace productivity, has announced a native integration with New Relic's AI agents, enabling engineering teams to perform observability-driven incident investigation directly within their Quick workspace. The integration leverages New Relic's remote Model Context Protocol (MCP) server to expose AI agent capabilities — including alert insights, log analysis, transaction diagnostics, user impact analysis, and natural language NRQL queries — through conversational prompts. This allows on-call engineers, SREs, and engineering leaders to investigate incidents, generate root cause analysis (RCA) documents, and create tracked tasks without context-switching between tools.

How It Works

• The integration is established by connecting Amazon Quick to New Relic's remote MCP server, which acts as a bridge exposing New Relic's AI agent capabilities as callable tools within Quick's conversational interface.
• Once connected, users can invoke New Relic agents via natural language prompts to query live observability data — including logs, traces, metrics, and alerts — using NRQL (New Relic Query Language) translated from plain English.
• Quick aggregates these live telemetry responses alongside enterprise knowledge stored in Quick Spaces (runbooks, architecture documents, on-call policies), providing contextually enriched answers that combine real-time system state with organizational knowledge.
• Additionally, Quick Flows — Quick's workflow automation layer — can programmatically invoke New Relic AI agents to automate recurring triage runbooks or escalation workflows.
• The output of an investigation can be compiled into a structured RCA document with evidence links and delivered as an email attachment, all within a single chat session.

Why It's Important

• Incident response traditionally requires engineers to context-switch across multiple tools — observability dashboards, documentation wikis, ticketing systems, and communication platforms — which increases mean time to resolution (MTTR) and cognitive load during high-stress outages.
• By unifying live telemetry from New Relic with organizational knowledge in a single conversational interface, this integration dramatically compresses the investigation-to-resolution workflow.
• The ability to generate a structured RCA document with evidence links in a single chat exchange is particularly valuable for post-incident reviews and compliance requirements, while Quick Flows automation enables teams to codify and consistently execute triage runbooks, reducing reliance on tribal knowledge and human error during incidents.

How It's Different

• Prior to this integration, using New Relic alongside an AI assistant would require either manual copy-pasting of telemetry data into a separate chat interface or building custom integrations using APIs.
• Existing observability-AI integrations in the market (such as using ChatGPT or Copilot with observability tools) typically lack deep contextual grounding in an organization's internal knowledge base.
• Amazon Quick's differentiator is the Spaces layer, which grounds AI responses in enterprise-specific context — runbooks, architecture docs, on-call policies — rather than relying solely on general model knowledge or raw telemetry.
• The use of the open MCP (Model Context Protocol) standard for the server connection also signals a more extensible, interoperable architecture compared to proprietary plugin systems, and Quick Flows adds a workflow automation dimension that goes beyond simple chat-based Q&A.

When to Prefer It

• This integration is best suited for organizations that are already using or evaluating New Relic as their primary observability platform and want to reduce tool sprawl during incident response.
• Teams that have invested in documenting runbooks, architecture diagrams, and on-call policies will see the greatest benefit, as Quick's Spaces layer will enrich telemetry-based answers with that institutional knowledge.
• It is particularly compelling for SRE and platform engineering teams that handle recurring incident patterns, since Quick Flows can automate triage runbooks and escalation paths.
• Organizations that require structured RCA documentation for compliance, SLA reporting, or blameless post-mortems will also find the automated RCA generation capability highly valuable.
• Teams not yet using New Relic or those with observability data spread across multiple platforms (e.g., Datadog, Grafana, Splunk) should evaluate whether New Relic consolidation aligns with their strategy before adopting this specific integration.

Availability

• The Amazon Quick integration with New Relic is generally available (GA) as of May 5, 2026.
• It is available in all AWS Regions where Amazon Quick is currently supported, though the announcement does not enumerate specific regions explicitly.
• There are no preview or beta caveats mentioned.
• Prerequisites include an active Amazon Quick account (sign-up is available via the Amazon Quick website) and access to a New Relic account with the ability to configure and connect to New Relic's remote MCP server.
• Additional integration details and setup instructions are available in the New Relic integration guide linked from the AWS announcement, and further Quick integrations can be explored on the Quick integrations page.