AWS DevOps Agent: What It Does and How to Get Started

At 2 AM, your deployment breaks. Your on-call engineer gets paged, spends 45 minutes correlating logs across CloudWatch, Datadog, and GitHub, and eventually pinpoints a bad commit. AWS DevOps Agent is designed to do that entire process autonomously — before the on-call engineer even wakes up.

On March 31, 2026, AWS DevOps Agent became generally available. This is the first AWS-native autonomous AI agent specifically built for DevOps and SRE work. Here's what it actually does, who it's for, and how to get started.

---

What AWS DevOps Agent Does

AWS DevOps Agent operates as a persistent, always-on operations agent that connects your observability stack, code repositories, runbooks, and CI/CD pipelines into a single reasoning layer.

Incident triage (autonomous): When an alert fires, the agent begins investigating immediately. It correlates telemetry from CloudWatch, Dynatrace, Datadog, Grafana, New Relic, or Splunk — then provides a root cause analysis and recommended resolution steps. United Airlines uses it to avoid 3 AM incident bridges: "Instead of initiating an incident call at 3 a.m. and switching between tools, we now have the answers ready."

Proactive recommendations: The agent doesn't just react. It analyzes patterns across historical incidents and produces recommendations across four areas: observability gaps, infrastructure optimization, deployment pipeline improvements, and application resilience. Each recommendation comes with agent-ready specs — ready to hand off to a coding agent or a colleague to implement.

CI/CD pipeline generation: Describe what you need in plain language. The agent generates pipeline configuration for your environment — AWS CodePipeline, GitHub Actions, GitLab CI, Azure DevOps.

Infrastructure and code analysis: Ask questions about your AWS architecture, Terraform configs, or CloudFormation stacks in natural language. Get contextual answers without digging through documentation.

Custom dashboards and reports: Create, save, and share custom charts from operational data — query resource health, track deployments, investigate incident patterns — all through a natural language interface.

---

Integrations

AWS DevOps Agent connects to:

Observability: Amazon CloudWatch, Dynatrace, Datadog, Grafana, New Relic, Splunk

Code and CI/CD: GitHub, GitLab, Azure DevOps (with your runbooks, code repositories, and deployment history)

Communication: Slack, ServiceNow, PagerDuty — routes findings and mitigation steps directly into your existing incident workflow

Custom integrations: Connect private or remote MCP servers to extend beyond the built-in list. This covers custom tools, proprietary ticketing systems, or specialized platforms your team already uses.

The agent builds a graph of your application resources and their relationships. This is what makes cross-tool correlation work — it understands that your Lambda function → ECS service → RDS cluster dependency chain, and traces incidents along it rather than treating each alert in isolation.

---

Who This Is For

DevOps and platform teams running production workloads on AWS who currently handle incident response manually or with fragmented tooling. The biggest ROI is at organizations where on-call rotations are burning people out and incident MTTR (mean time to resolve) is measured in hours.

SRE teams who want continuous proactive recommendations without maintaining a separate backlog of reliability improvements. The agent's proactive mode surfaces actionable items automatically.

Small engineering teams where there's no dedicated SRE function — the agent acts as a lightweight SRE layer on top of existing AWS infrastructure.

What it's not: A replacement for your senior engineers. It handles investigation, correlation, and initial recommendations — but code changes, architectural decisions, and production rollbacks still need human sign-off. Think of it as a very thorough junior DevOps engineer who never sleeps.

---

How to Get Started

AWS DevOps Agent is available now in the AWS Management Console.

Step 1: Enable AWS DevOps Agent

Go to aws.amazon.com/devops-agent → click "Get started" → follow the console setup wizard. You'll need an AWS account with appropriate IAM permissions (CloudWatch read, CodePipeline read, and access to connected observability tools).

Step 2: Connect your observability stack

In the setup wizard, connect your monitoring tools. AWS CloudWatch connects automatically via your account. For Datadog, Dynatrace, Grafana, New Relic, or Splunk, you'll provide API keys and endpoint URLs.

Step 3: Connect code repositories

Link GitHub or GitLab repos. The agent uses deployment history and code context when analyzing incidents — a deploy 6 minutes before an alert fires is meaningful signal.

Step 4: Import runbooks

Upload your existing runbooks (Confluence, Notion, markdown files) as context. The agent references these during incident analysis instead of treating every incident as novel.

Step 5: Configure alerting channels

Set up Slack or PagerDuty routing. When the agent identifies a root cause, it sends findings directly to your incident channel — formatted as an investigation summary with actions.

---

Pricing

AWS DevOps Agent uses a consumption-based model tied to the number of agent actions and connected resources. Pricing details are in the AWS Console under the DevOps Agent service page. For most mid-size teams, the agent's cost should be a fraction of on-call engineer time saved per month — but worth modeling for your own environment before full rollout.

---

Key Takeaways

• What it is: AWS-native autonomous DevOps agent — incident triage, root cause analysis, CI/CD generation, proactive SRE recommendations
• GA date: March 31, 2026
• Integrations: CloudWatch, Dynatrace, Datadog, Grafana, New Relic, Splunk, GitHub, GitLab, Slack, PagerDuty, ServiceNow, MCP servers
• Best for: DevOps/SRE teams managing production AWS workloads at scale
• Not a replacement for: Senior engineers, architectural decisions, or production rollbacks requiring human judgment
• Get started: aws.amazon.com/devops-agent