AWS Systems Manager Incident Manager
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey29 EndpointsREST
For Agents
Coordinate on-call response to AWS incidents through Incident Manager. Agents can start incidents, attach timeline events, manage response plans, and update incident records.
Use for: I need to start a new incident from an existing response plan, Append a timeline event to an active incident, List all open incident records in the last 24 hours, Update the impact level of an active incident from 3 to 1
Not supported: Does not collect metrics, evaluate alarms, or run runbook automation directly — use for orchestrating the incident lifecycle and response plans only.
Jentic publishes the only available OpenAPI specification for AWS Systems Manager Incident Manager, keeping it validated and agent-ready. Incident Manager helps responders mitigate and recover from outages affecting AWS-hosted applications by automating response plans, escalation, and incident-record collaboration. Agents can create response plans with engagement contacts and runbooks, start incidents with StartIncident, append timeline events, list and update incident records, and manage cross-region replication sets. The 29 operations cover incident records, response plans, replication sets, timeline events, related items, and resource policies.
Install Jentic One Beta
Connect the AWS Systems Manager Incident Manager to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Systems Manager Incident Manager, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 AWS Systems Manager Incident Manager API.
Create response plans with engagements, runbooks, and escalation chains via CreateResponsePlan
Start a new incident from a response plan using StartIncident
Append timeline events to an open incident with CreateTimelineEvent
Update incident impact, status, and summary fields with UpdateIncidentRecord
Attach related items (Jira tickets, runbook links, dashboards) via UpdateRelatedItems
Manage cross-region replication sets so incident data survives a regional outage
Apply resource-based policies to share response plans across accounts
Use Cases
Patterns agents use AWS Systems Manager Incident Manager API for, with concrete tasks.
★ Automated Paging When CloudWatch Alarms Trigger
Operations teams wire CloudWatch alarms to Incident Manager response plans so that an alarm in ALARM state automatically starts an incident, pages the on-call engagement, and opens the runbook. Agents can create the plan with CreateResponsePlan referencing engagements and runbook ARNs, then leave incident creation to EventBridge.
CreateResponsePlan with name='checkout-p1', a high-impact value, an Engagements array referencing the Incident Manager contact ARN, and a SsmAutomation block pointing at a runbook document.
Incident Record Enrichment During Triage
During an active incident, responders enrich the record with context: posting timeline events as new findings emerge, attaching Jira tickets and dashboard URLs as related items, and updating the impact field as the blast radius is understood. The incident record becomes the canonical source for post-incident review.
Call CreateTimelineEvent on the open incident with eventType=Custom Event and eventData='Database failover initiated', then UpdateRelatedItems to add a Jira link with itemType=ATTACHMENT.
Multi-Region Replication Set Setup
Incident Manager replicates incident data across regions so a regional outage does not destroy the operating record. CreateReplicationSet defines the regions, GetReplicationSet inspects state, and UpdateReplicationSet adds or removes regions when the topology changes.
CreateReplicationSet with two regions (us-east-1 and us-west-2), then GetReplicationSet to confirm Status=ACTIVE in both.
AI Agent Incident Triage via Jentic
AI agents using Jentic can drive incident operations from chat: starting incidents, posting timeline updates, and attaching related items as the situation evolves. Through Jentic, the agent searches by intent, loads the operation schema, and executes against vault-stored AWS credentials.
Search Jentic for 'start an incident from a response plan', execute StartIncident with the response plan ARN and an impact of 2, then CreateTimelineEvent to record the agent's first observation.
Key Endpoints
29 endpoints — jentic publishes the only available openapi specification for aws systems manager incident manager, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/createResponsePlan
Create a reusable response plan
POST
/createTimelineEvent
Append a timeline event to an incident
GET
/getIncidentRecord#arn
Fetch an incident record by ARN
POST
/listIncidentRecords
List incident records with optional filters
POST
/createReplicationSet
Create a cross-region replication set
GET
/getReplicationSet#arn
Get the replication set configuration
POST
/listRelatedItems
List related items attached to an incident
POST
/deleteIncidentRecord
Delete an incident record
POST
/createResponsePlan
Create a reusable response plan
POST
/createTimelineEvent
Append a timeline event to an incident
GET
/getIncidentRecord#arn
Fetch an incident record by ARN
POST
/listIncidentRecords
List incident records with optional filters
POST
/createReplicationSet
Create a cross-region replication set
GET
/getReplicationSet#arn
Get the replication set configuration
POST
/listRelatedItems
List related items attached to an incident
POST
/deleteIncidentRecord
Delete an incident record
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys are stored encrypted in the Jentic vault. Each Incident Manager call is signed with SigV4 inside Jentic, so raw credentials never appear in the agent's prompt.
Intent-based discovery
Agents search by intent (for example, 'start an incident' or 'append a timeline event') and Jentic returns the matching Incident Manager operations with input schemas, letting the agent invoke StartIncident or CreateTimelineEvent directly.
Time to first call
Direct Incident Manager integration: 2-3 days for IAM, SigV4 signing, response plan modelling, and replication set setup. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Systems Manager Incident Manager API through Jentic.
Why is there no official OpenAPI spec for AWS Systems Manager Incident Manager?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Systems Manager Incident Manager via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AWS Systems Manager Incident Manager use?
Incident Manager uses AWS Signature Version 4 with IAM credentials and permissions on the ssm-incidents:* actions. Through Jentic, the AWS access key and secret are stored encrypted in the vault — Jentic signs each call before forwarding it to the regional Incident Manager endpoint.
Can I start an incident programmatically?
Yes. StartIncident creates an incident record from an existing response plan ARN. The call accepts impact (1-5), title, triggerDetails, and an optional relatedItems array. Engagements defined on the response plan execute automatically once the incident starts.
What are the rate limits for the AWS Systems Manager Incident Manager?
Incident Manager applies standard AWS API throttling — most operations are limited to a few requests per second per account per region with short bursts. Throttled requests return ThrottlingException; clients should retry with exponential backoff.
How do I append a timeline event to an open incident through Jentic?
Through Jentic, search for 'create timeline event incident manager', load the CreateTimelineEvent schema, and execute with the incidentRecordArn, eventType, eventData, and eventTime. Jentic returns the eventId for follow-up updates.
Is AWS Systems Manager Incident Manager free?
Incident Manager charges per incident started, per engagement, and per response plan run. SMS and voice-call engagements have additional per-event costs; see https://aws.amazon.com/systems-manager/pricing/incident-manager/ for the current rates.
GET STARTED