AWS DevOps Agent Database Skill: Their 73 Percent MTTR Figure (2026)
Quick summary: 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.
Key Takeaways
- 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
- On 17 November 2026, AWS published a custom skill for AWS DevOps Agent 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
- Key facts (verified 2026-11-18) - The number
- 52 minutes to 14 minutes, 73 percent, three simulated incidents

Table of Contents
On 17 November 2026, AWS published a custom skill for AWS DevOps Agent 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.
What broke
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 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.
- 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.
- Preview figures, kept separate: the GA claims cited from that post are discussed on the MCP security note.
Frequently asked questions
Is the 73 percent MTTR cut a FactualMinds result?
When should we NOT add a database skill?
When is a skill the wrong incident tool even if telemetry exists?
Does the 75 percent preview figure replace the 73 percent test?

AWS Cloud Architect & AI Expert
AWS-certified cloud architect and AI expert with deep expertise in cloud migrations, cost optimization, and generative AI on AWS.




