AWS Amazon DevOps Guru
Browse all Amazonaws APIs61
AI ReadinessAI-Aware (B-)61/100
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilityhmac31 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Retrieve DevOps Guru insights, anomalies, and recommendations, configure resource collections, and route notifications to downstream incident workflows.
Use for: List proactive and reactive insights for the last 7 days, Get anomalies that contributed to a specific insight, Update the resource collection to track a new CloudFormation stack, Add an SNS topic as a DevOps Guru notification channel
Not supported: Does not handle remediation, log ingestion, or metric publishing - use for retrieving operational insights and configuring DevOps Guru analysis only.
Jentic publishes the only available OpenAPI specification for Amazon DevOps Guru, keeping it validated and agent-ready. Amazon DevOps Guru is a managed service that uses machine learning over CloudWatch metrics and CloudTrail events to detect anomalous behaviour in operational AWS workloads. The API lets you scope which resources DevOps Guru analyses, retrieve insights, anomalies, and recommendations, configure SNS notification channels, and set up Systems Manager OpsItem integration. Use it when an agent needs to automate insight triage or wire DevOps Guru output into existing incident workflows.
Install Jentic One Beta
Connect the Amazon DevOps Guru to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon DevOps Guru, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-devops-guru" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-devops-guru" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Amazon DevOps Guru API.
Configure which AWS resources are analysed via UpdateResourceCollection scoped by CloudFormation stacks or tags
List and inspect operational insights with ListInsights, DescribeInsight, and SearchInsights
Pull related anomalies for an insight using ListAnomaliesForInsight to get supporting metrics and time ranges
Subscribe SNS topics for new insight notifications via AddNotificationChannel and RemoveNotificationChannel
Enable Systems Manager OpsItem creation per insight through UpdateServiceIntegration
Provide feedback on insight usefulness with PutFeedback to tune future detection
Use Cases
Patterns agents use Amazon DevOps Guru API for, with concrete tasks.
★ Triage Operational Insights into Tickets
Wire DevOps Guru into the existing incident process by scoping resource collections to production CloudFormation stacks and routing every new insight to an SNS topic that fans out to PagerDuty or Slack. ListInsights and DescribeInsight let an agent enrich each alert with the underlying anomalies and recommended actions before paging a human.
Call AddNotificationChannel with an SNS topic ARN, then ListInsights filtered to the last 24 hours and DescribeInsight on each to enrich the ticket payload.
Scope Detection to a Production Workload
Use UpdateResourceCollection to point DevOps Guru at the CloudFormation stacks or tag set that defines the production workload, ensuring insights focus on business-critical resources rather than every account resource. ListInsights then returns only the relevant anomalies, keeping signal-to-noise high.
Call UpdateResourceCollection with ResourceCollection.CloudFormation.StackNames set to the prod stacks and verify with GetResourceCollection.
Auto-Create OpsItems for Each Insight
Enable Systems Manager OpsItem creation via UpdateServiceIntegration so every reactive insight automatically appears in the Systems Manager OpsCenter queue alongside the rest of the operations backlog. Engineers see the insight, recommendations, and related events in one place without polling DevOps Guru directly.
Call UpdateServiceIntegration with OpsCenter.OptInStatus set to ENABLED and confirm via DescribeServiceIntegration.
Agent-Driven Insight Triage
An AI agent connected via Jentic can poll DevOps Guru, pull the anomalies and recommendations that back each new insight, and decide whether to file a ticket, page on-call, or close as known. Jentic returns the matching DevOps Guru operation and schema so the agent can compose a multi-step triage flow without bespoke AWS SDK code.
Search Jentic for 'list DevOps Guru insights', load ListInsights, execute it with a 24-hour StartTimeRange, then DescribeInsight on each result and ListAnomaliesForInsight to assemble the triage context.
Key Endpoints
31 endpoints — jentic publishes the only available openapi specification for amazon devops guru, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/insights/{Id}
Describe a specific insight
GET
/anomalies/{Id}
Describe a specific anomaly
POST
/anomalies/insight/{InsightId}
List anomalies for an insight
POST
/channels
Add a notification channel
PUT
/service-integrations
Enable Systems Manager OpsItem integration
PUT
/event-sources
Update event source configuration
PUT
/feedback
Submit feedback on an insight
GET
/insights/{Id}
Describe a specific insight
GET
/anomalies/{Id}
Describe a specific anomaly
POST
/anomalies/insight/{InsightId}
List anomalies for an insight
POST
/channels
Add a notification channel
PUT
/service-integrations
Enable Systems Manager OpsItem integration
PUT
/event-sources
Update event source configuration
PUT
/feedback
Submit feedback on an insight
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Amazon DevOps Guru
- AI-Aware (B-)61/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
38
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
52%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Amazon DevOps Guru by hand means building SigV4 request signing, resolving the regional devops-guru.{region}.amazonaws.com host, and handling AWS throttling and retries yourself. Through Jentic you install once, import DevOps Guru from the API Directory, store the AWS access keys once, and your agent calls it.
Permission scoping
DevOps Guru puts the insight id in the URL path (/insights/{Id}), so a rule can pin your agent to one insight: it can read that insight and its anomalies and nothing else. You choose the operations it may call, so write actions like updating service integrations or event sources are not included unless you add them.
Credential isolation
Your AWS access keys for DevOps Guru are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list DevOps Guru insights' or 'add an SNS notification channel', and Jentic returns the matching DevOps Guru operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon DevOps Guru API through Jentic.
Why is there no official OpenAPI spec for Amazon DevOps Guru?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon DevOps Guru via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Amazon DevOps Guru API use?
DevOps Guru uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in your Jentic One instance and are injected into signed requests at execution time, so the agent never sees the raw secret access key.
Can I limit DevOps Guru to a specific CloudFormation stack?
Yes. Call UpdateResourceCollection with ResourceCollection.CloudFormation.StackNames set to the stacks you want analysed. DevOps Guru will then constrain insights and anomalies to resources defined in those stacks.
What are the rate limits for the Amazon DevOps Guru API?
DevOps Guru shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. Bulk insight retrieval should use pagination via NextToken and back off on ThrottlingException responses.
How do I get DevOps Guru insights into Slack via Jentic?
Search Jentic for 'list DevOps Guru insights', load ListInsights, execute it on a schedule, and forward the response to a Slack-posting operation also discovered via Jentic. Run pip install jentic and use the async search and execute pattern.
Does this API trigger remediation, or only surface findings?
The API surfaces insights, anomalies, and recommendations. Acting on a recommendation requires calling the underlying AWS service API (such as Auto Scaling or Lambda) directly - DevOps Guru itself does not execute remediation.
Can I limit what my agent is allowed to do with the Amazon DevOps Guru API?
Yes. Jentic One runs self-hosted, so your own rules decide which DevOps Guru operations and credentials your agent may use. Because the insight id sits in the URL path (/insights/{Id}), you can pin the agent to a single insight so it reads only that insight and its anomalies and nothing else. You pick the operations it may call, so write actions like UpdateServiceIntegration or event-source changes stay off limits until you explicitly allow them.
GET STARTED