Amazon DevOps Guru
An AIOps service that uses machine learning to automatically detect operational anomalies, estimate root causes, and provide remediation recommendations
Overview
Amazon DevOps Guru is an AIOps service that uses machine learning to automatically detect operational anomalies in applications, estimate root causes, and provide specific remediation recommendations. It continuously analyzes CloudWatch metrics, CloudTrail logs, and Config change history, reporting deviations from normal operational patterns as insights. It detects operational issues in serverless and container environments - such as increased Lambda cold starts, DynamoDB throttling, and abnormal ECS task termination patterns - without relying on manual monitoring.
Insight Types and Anomaly Detection Mechanics
AWS has announced that DevOps Guru does not accept new customers from October 29, 2026, and that support ends on September 30, 2027. Customers who signed up before that date can use it until the end date, and AWS points to Amazon CloudWatch as the alternative. Insights generated by DevOps Guru fall into two categories: reactive insights and proactive insights. Reactive insights are generated when an active anomaly is detected. For example, when API Gateway latency spikes, it correlates related Lambda function error rate increases and DynamoDB throttling to present root cause candidates. Proactive insights detect signs that haven't yet caused failures but could become problems if left unaddressed. Examples include DynamoDB table capacity consumption trending upward or Lambda concurrent executions approaching the limit. Anomaly detection uses machine learning, and users don't need to train their own models.
Coverage Settings and Resource Grouping
DevOps Guru's monitoring scope can be narrowed to the entire AWS account, specific CloudFormation stacks, or specific tags. When specifying by CloudFormation stack, all resources within the stack (Lambda, DynamoDB, API Gateway, SQS, etc.) are automatically added to the monitoring scope. Tag-based specification uses only one tag key; for example, you can tag resources with the key devops-guru-applications and use a different value for each application. DevOps Guru groups the resources in each selected stack, or with each tag value, into an application for analysis. In microservices architectures, separating CloudFormation stacks per service lets you treat each service as its own application. The official pricing page states that charges are based on the number of active resource hours analyzed (with resource types divided into two pricing groups) and the number of DevOps Guru API calls (as of October 2026).
Notification Channels and Operational Workflows
DevOps Guru insights are delivered to operations teams through Amazon SNS topics. When an SNS topic is configured, messages are published on new insight generation, insight severity upgrades, and insight closure. Forwarding SNS notifications to a Slack channel via Amazon Q Developer in chat applications (formerly AWS Chatbot) lets the team review insights within their everyday communication tool. EventBridge integration is also available, enabling different actions to be triggered based on insight type and severity. For example, you can page the on-call responder via PagerDuty for high-severity reactive insights while limiting medium and below to Slack notifications. The insight detail view displays graphs of the metrics where anomalies were detected, a list of related resources, and recommended remediation actions.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
- Amazon CloudWatch official page
- AWS CloudTrail official page
- AWS Config official page
- AWS Documentation (official)
If this page and the official documentation disagree, treat the official documentation as authoritative.