---
title: AWS DevOps Agent Database Skill: Their 73 Percent MTTR Figure (2026)
description: On 17 November 2026 AWS reported a database skill that cut mean time to resolution from 52 minutes to 14 minutes, a 73 percent reduction, in a controlled test of three simulated incidents. That number is theirs. A skill is the wrong tool when there is no runbook, no telemetry, or a write with no approval.
url: https://www.factualminds.com/blog/aws-devops-agent-database-incident-mttr-2026/
datePublished: 2026-11-18T00:00:00.000Z
dateModified: 2026-11-18T00:00:00.000Z
author: palaniappan-p
category: DevOps & CI/CD
tags: aws, devops, ai-agents, amazon-aurora, cloudwatch, incident-response
---

# AWS DevOps Agent Database Skill: Their 73 Percent MTTR Figure (2026)

> On 17 November 2026 AWS reported a database skill that cut mean time to resolution from 52 minutes to 14 minutes, a 73 percent reduction, in a controlled test of three simulated incidents. That number is theirs. A skill is the wrong tool when there is no runbook, no telemetry, or a write with no approval.

On **17 November 2026**, AWS published a [custom skill for AWS DevOps Agent](https://aws.amazon.com/blogs/devops/reduce-database-incident-mttr-by-73-with-aws-devops-agent-custom-skills/) that, in their words, reduces mean time to resolution from **52 minutes to 14 minutes**. That is a **73 percent** reduction, measured in a **controlled internal test of three simulated incidents**. The database is Aurora PostgreSQL. The skill is a markdown procedure the agent reads. It is not an executable, and it is not something we delivered.

## Key facts (verified 2026-11-18)

- **The number.** 52 minutes to 14 minutes, 73 percent, three simulated incidents. Source is the AWS DevOps blog on 17 November 2026. Not a customer engagement and not our lab.
- **What the skill covers.** Five failure modes in one procedure: connection pool exhaustion, replica lag, a slow query with high CPU, storage and bloat, and parameter drift. AWS says the skill needs CloudWatch and Performance Insights.
- **What a skill is.** A `SKILL.md` plus references, in the agentskills.io layout they cite. The agent follows the text. The text does not run SQL by itself.
- **The other percentage.** Preview customers, in the GA announcement that post cites, saw up to 75 percent lower MTTR. That is a separate claim. Do not average it with 73.

## What broke

> **What broke:** AWS's test is three simulated database incidents, not a production outage we observed. The failure the skill is aimed at is a person re-deriving the same five checks from scratch while the clock runs. Detection is an alarm you already trust. Recovery in their design is the skill walking those checks. Lesson: if the alarm is noisy, the skill makes the noise faster.

A skill with permission to change a parameter group will apply a wrong diagnosis. Keep the first version read-only. A named reviewer approves a write, the same way a runbook's change step already requires a person.

## When the skill is the wrong tool

No runbook. If the on-call steps live in someone's head, a skill copies that gap into a file and then follows it. Write the five checks down first. Then decide whether an agent should read them.

No telemetry. Connection pool, replica lag, CPU, storage, and parameter drift each need a metric or a log you already collect. Performance Insights off means the slow-query branch has nothing to read.

Write access. Restart, failover, and `ALTER SYSTEM` are not investigation. The diagram on this page stops at a named reviewer. [MCP for DevOps Agent](https://www.factualminds.com/blog/mcp-security-enterprise-ai-2026/) is the separate question of which tools the agent may call.

## What this post doesn't cover

- A second MTTR study. We are not adding a number of our own.
- How to enable AWS DevOps Agent in an account. Use the AWS console path. This page is the skill boundary.
- FIS game days. Fault injection on a contact center or a Region switch stays on the [DevOps practice list](https://www.factualminds.com/blog/10-aws-devops-practices-production-2026/).
- AgentCore as the incident runner. This product is AWS DevOps Agent. Gateway and Runtime are a different stack.

## Sources

- AWS DevOps blog, 17 November 2026, [Reduce database incident MTTR by 73% with AWS DevOps Agent custom skills](https://aws.amazon.com/blogs/devops/reduce-database-incident-mttr-by-73-with-aws-devops-agent-custom-skills/).
- Preview figures, kept separate: the GA claims cited from that post are discussed on the [MCP security note](https://www.factualminds.com/blog/mcp-security-enterprise-ai-2026/).

## FAQ

### Is the 73 percent MTTR cut a FactualMinds result?
No. AWS's 17 November 2026 DevOps blog says a custom Aurora PostgreSQL skill reduced mean time to resolution from 52 minutes to 14 minutes, a 73 percent reduction, in a controlled internal test of three simulated incidents. We did not run that test and we are not publishing it as delivery proof.

### When should we NOT add a database skill?
Skip it when you have no written runbook, when CloudWatch and Performance Insights are not already on the cluster, or when the skill would change parameters, restart a database, or fail over without a named person. A markdown file cannot see a metric you do not emit, and a write during an incident is how a bad diagnosis becomes an outage.

### When is a skill the wrong incident tool even if telemetry exists?
When the failure is outside the five modes the skill names, or when two incidents need two different approvals. AWS's skill covers connection pool exhaustion, replica lag, a slow query with high CPU, storage and bloat, and parameter drift. A skill that guesses past that list will sound specific and be wrong. Page a person.

### Does the 75 percent preview figure replace the 73 percent test?
No. The DevOps Agent GA note cites preview customers at up to 75 percent lower MTTR, 80 percent faster investigations, and 94 percent root-cause accuracy. That is a different AWS claim, about the product in preview, not about this three-incident database test. Keep them apart. The MCP post dates the preview figures.

---

*Source: https://www.factualminds.com/blog/aws-devops-agent-database-incident-mttr-2026/*
