AWS Systems Manager Incident Manager is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see [AWS Systems Manager Incident Manager availability change](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-availability-change.html). # Document history for Incident Manager | Change | Description | Date | | --- |--- |--- | | [AWS Systems Manager Incident Manager published migration docs](#doc-history) | Incident Manager has published migration docs to help customers understand some of the options available to migrate from AWS Systems Manager Incident Manager. For more information, see [AWS Systems Manager Incident Manager availability change](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-availability-change.html). | November 21, 2025 | | [Update to managed policy `AWSIncidentManagerResolverAccess`](#doc-history) | Incident Manager has updated the managed policy `AWSIncidentManagerResolverAccess` to add ssm-contacts:StartEngagement permission for starting engagements with contacts during incidents. For more information, see [Incident Manager updates to AWS managed policies](https://docs.aws.amazon.com/incident-manager/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-updates). | November 20, 2025 | | [AWS Systems Manager Incident Manager is no longer open to new customers.](#doc-history) | AWS Systems Manager Incident Manager is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see [AWS Systems Manager Incident Manager availability change](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-availability-change.html). | November 7, 2025 | | [AWS Systems Manager Incident Manager will no longer be open to new customers starting November 7, 2025.](#doc-history) | AWS Systems Manager Incident Manager will no longer be open to new customers starting November 7, 2025. If you would like to use Incident Manager, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see [AWS Systems Manager Incident Manager availability change](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-availability-change.html). | October 7, 2025 | | [Change to permission requirements for creating incidents manually](#doc-history) | The IAM permissions required for a user to create an incident manually have changed and no longer use a service-linked role. Instead, Incident Manager now uses [forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html) (FAS) to call `ssm-contacts:StartEngagement` as part of `ssm-incidents:StartIncident`. For more information, see [Required IAM permissions for manually starting incidents](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-creation.html#incident-tracking-manual-permissions). | June 10, 2025 | | [Update to managed policy `AWSServiceRoleforIncidentManagerPolicy`](#doc-history) | Incident Manager has added a new permission to `AWSServiceRoleforIncidentManagerPolicy` that allows Incident Manager to publish metrics within the `AWS/Usage` namespace into your account. For more information, see [Incident Manager updates to AWS managed policies](https://docs.aws.amazon.com/incident-manager/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-updates). | January 28, 2025 | | [Update to managed policy `AWSIncidentManagerIncidentAccessServiceRolePolicy`](#doc-history) | Incident Manager has added a new permission to `AWSIncidentManagerIncidentAccessServiceRolePolicy`, in support of the Findings feature, that allows it to check whether an EC2 instance is part of an Auto Scaling group. For more information, see [Incident Manager updates to AWS managed policies](https://docs.aws.amazon.com/incident-manager/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-updates). | February 20, 2024 | | [Additional HashiCorp Terraform support: On-call rotations](#doc-history) | Terraform has added to its support for Incident Manager. You can now provision or manage Incident Manager on-call resources using Terraform. For information about this and other third-party integrations with Incident Manager, see [Integration with other products and services](https://docs.aws.amazon.com/incident-manager/latest/userguide/integration.html#integrations-other). | February 2, 2024 | | [New feature: Findings from other AWS services](#doc-history) | *Findings* provide you with information about changes related to AWS CloudFormation stacks and AWS CodeDeploy deployments that occurred around the same time that an incident was created in Incident Manager. In the Incident Manager console, you can view summary information about those changes and, in many cases, access links to the CloudFormation or CodeDeploy consoles for complete details about the change. Findings reduce the time required to evaluate potential causes of incidents. They also reduce the chances of responders accessing the wrong account or console to investigate the cause of an incident. This feature also introduces a new managed policy, `AWSIncidentManagerIncidentAccessServiceRolePolicy`, which allows Incident Manager to read resources in other AWS services to identify findings related to incidents. For more information, see the following topics: [Working with findings](https://docs.aws.amazon.com/incident-manager/latest/userguide/findings.html) [AWS managed policy: AWSIncidentManagerIncidentAccessServiceRolePolicy](https://docs.aws.amazon.com/incident-manager/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AWSIncidentManagerIncidentAccessServiceRolePolicy) | November 15, 2023 | | [Updated lists of integrations with Incident Manager](#doc-history) | The topic [Product and service integrations with Incident Manager](https://docs.aws.amazon.com/incident-manager/latest/userguide/integration.html) has been expanded to list and describe all AWS services and third-party tools that you can integrate with Incident Manager into your incident detection and response operations. | June 9, 2023 | | [Integration with AWS Trusted Advisor](#doc-history) | Trusted Advisor now checks that a replication set’s configuration uses more than one AWS Region to support regional failover and response. For incidents created by CloudWatch alarms or EventBridge events, Incident Manager creates an incident in the same AWS Region as the alarm or event rule. If Incident Manager is temporarily unavailable in that Region, the system attempts to create an incident in another Region in the replication set. If the replication set includes only one Region, the system fails to create an incident record while Incident Manager is unavailable. To help avoid this situation, Trusted Advisor reports when a replication set is configured for only one Region. For information about working with Trusted Advisor, see [AWS Trusted Advisor](https://docs.aws.amazon.com//awssupport/latest/user/trusted-advisor.html) in the *AWS Support User Guide*. | April 28, 2023 | | [Use Microsoft Teams as a chat channel in response plans](#doc-history) | Through integration with Microsoft Teams and Amazon Q Developer in chat applications, you can now use Microsoft Teams for the chat channel in your response plans. This is in addition to support for Slack and Amazon Chime chat channels. During an incident, Incident Manager sends status notifications directly to a chat channel to keep all responders informed. Responders can also communicate with one another and incident-related AWS CLI commands in the Microsoft Teams application to update and interact with the incidents. For more information, see [Working with chat channels in Incident Manager](https://docs.aws.amazon.com/incident-manager/latest/userguide/chat.html). | April 4, 2023 | | [New feature: On-call schedules](#doc-history) | An on-call schedule in Incident Manager defines who is notified when an incident occurs that requires operator intervention. An on-call schedule consists of one or more rotations you create for the schedule. Each rotation can include up to 30 contacts. After you create an on-call schedule, you can include it as an escalation in your escalation plan. When an incident associated with that escalation plan occurs, Incident Manager notifies the operator (or operators) who are on call according to the schedule. For more information, see [Working with on-call schedules in Incident Manager](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-on-call-schedule.html). | March 28, 2023 | | [Print a formatted incident analysis or save as PDF](#doc-history) | The incident analysis page now includes a **Print** button to generate a version of the analysis that's formatted for printing. Using the printer destinations configured for your device, you can save the incident analysis as a PDF or send it to a local or network printer. For more information, see [Print a formatted incident analysis](https://docs.aws.amazon.com/incident-manager/latest/userguide/analysis.html#print-a-formatted-analysis). | January 17, 2023 | | [PagerDuty integration: Incident Manager now copies incident timeline events to PagerDuty incidents](#doc-history) | When you turn on integration with PagerDuty in a response plan, Incident Manager adds timeline events created from that plan to the corresponding incident record in PagerDuty. PagerDuty adds timeline events as notes on the incident, up to a maximum of 2,000 notes. To learn more about these changes, see the following topics: [Store PagerDuty access credentials in an AWS Secrets Manager secret](https://docs.aws.amazon.com/incident-manager/latest/userguide/integrations-pagerduty-secret.html) [Integrate a PagerDuty service into the response plan](response-plans.md#anchor-pagerduty) | December 15, 2022 | | [Incident Manager integration with CloudWatch metrics.](#doc-history) | You can now have incident-related metrics published in CloudWatch. For more information, see [CloudWatch metrics.](https://docs.aws.amazon.com/incident-manager/latest/userguide/cloudwatch-metrics.html) The [ AWSIncidentManagerServiceRolePolicy ](https://docs.aws.amazon.com/incident-manager/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AWSServiceRoleforIncidentManagerPolicy) has included an additional permission to allow our service to publish metrics on your behalf. | December 15, 2022 | | [Launched **Incident notes** and updated the **Incident Details** screen.](#doc-history) | You can collaborate and communicate with other users that work on an incident using **Incident notes**. Additionally, you can view runbooks and engagements statuses from the **Incident Details** screen. For more information, see [Incident Details.](https://docs.aws.amazon.com/incident-manager/latest/userguide/tracking-details.html) | November 16, 2022 | | [Launched **Incident notes** and updated the **Incident Details** screen](#doc-history) | You can collaborate and communicate with other users that work on an incident using **Incident notes**. Additionally, you can view runbooks and engagements statuses from the **Incident Details** screen. For more information, see [Incident Details.](https://docs.aws.amazon.com/incident-manager/latest/userguide/tracking-details.html) | November 16, 2022 | | [Integrate PagerDuty escalation plans and paging workflows into Incident Manager response plans](#doc-history) | You can now integrate Incident Manager with PagerDuty and add a PagerDuty service to a response plan. After you configure integration, Incident Manager can create a corresponding incident in PagerDuty for each new incident created in Incident Manager. PagerDuty uses the paging workflow and escalation policies you define in the PagerDuty environment.For more information, see the following topics: [Product and service integrations with Incident Manager](https://docs.aws.amazon.com/incident-manager/latest/userguide/integration.html) [Store PagerDuty access credentials in an AWS Secrets Manager secret](https://docs.aws.amazon.com/incident-manager/latest/userguide/integrations-pagerduty-secret.html) [Integrate a PagerDuty service into the response plan](response-plans.md#anchor-pagerduty) in the topic [Creating a response plan](response-plans.md#response-plans-create) [Troubleshooting](https://docs.aws.amazon.com/incident-manager/latest/userguide/troubleshooting.html) | November 16, 2022 | | [Tagging support for replication sets](#doc-history) | You can now assign tags to your replication set in AWS Systems Manager Incident Manager. This adds to existing support for assigning tags to response plans, incident records, and contacts in the AWS Regions specified in your replication set. For information, see the following topics: [Get prepared wizard](https://docs.aws.amazon.com/incident-manager/latest/userguide/getting-started.html#getting-started-wizard) [Tagging Incident Manager resources](https://docs.aws.amazon.com/incident-manager/latest/userguide/tagging.html) | November 2, 2022 | | [Incident Manager integration with Atlassian Jira Service Management](#doc-history) | You can integrate Incident Manager with [Jira Service Management](https://www.atlassian.com/software/jira/service-management) by using the AWS Service Management Connector for Jira Service Management. After you configure integration, new incidents created in Incident Manager create a corresponding incident in Jira. If you update an incident in Incident Manager, the updates are added to the corresponding incident in Jira. If you resolve an incident in either Incident Manager or Jira, the corresponding incident is also resolved, based on configured preferences. For more information, see [Configuring Jira Service Management](https://docs.aws.amazon.com/smc/latest/ag/jsd-integration-configure-jsd.html) in the *AWS Service Management Connector Administrator Guide*. | October 6, 2022 | | [Enhanced tagging support](#doc-history) | Incident Manager supports assigning tags to response plans, incident records, and contacts in the AWS Regions specified in your replication set. Incident Manager also supports automatically assigning tags to incidents created from response plans. For more information, see [Tagging Incident Manager resources](https://docs.aws.amazon.com/incident-manager/latest/userguide/tagging.html). | June 28, 2022 | | [Incident Manager integration with ServiceNow](#doc-history) | You can integrate Incident Manager with [ServiceNow](https://www.servicenow.com/) by using the AWS Service Management Connector for ServiceNow. After you configure integration, new incidents created in Incident Manager create a corresponding incident in ServiceNow. If you update an incident in Incident Manager, the updates are added to the corresponding incident in ServiceNow. If you resolve an incident in either Incident Manager or ServiceNow, the corresponding incident is also resolved, based on configured preferences. For more information, see [Integrating AWS Systems Manager Incident Manager in ServiceNow](https://docs.aws.amazon.com/servicecatalog/latest/smcguide/sn-im.html). | June 9, 2022 | | [Import contact details](#doc-history) | When an incident is created, Incident Manager can notify responders by using voice or SMS notifications. To ensure that responders see that the call or SMS notification is from Incident Manager, we recommend that all responders download the Incident Manager virtual card format (.vcf) file to the address book on their mobile devices. For more information, see [Import contact details to your address book](https://docs.aws.amazon.com/incident-manager/latest/userguide/contacts.html#contacts-details-file). | May 18, 2022 | | [Multiple feature improvements to enhance incident creation and remediation](#doc-history) | Incident Manager launched the following feature improvements to enhance incident creation and remediation: **Automatically create incidents in other AWS Regions**: In the event that Incident Manager is not available in an AWS Region when Amazon CloudWatch or Amazon EventBridge create an incident, these services now automatically create the incident in one of the available Regions specified in your replication set. For more information, see [Cross-Region incident management](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-manager-cross-account-cross-region.html#incident-manager-cross-region). **Automatically populate runbook parameters with incident metadata**: You can now configure Incident Manager to collect information about AWS resources from incidents. Incident Manager can then populate runbook parameters with the collected information. For more information, see [Tutorial: Using Systems Manager Automation runbooks with Incident Manager](https://docs.aws.amazon.com//incident-manager/latest/userguide/tutorials-runbooks.html). **Automatically collect AWS resource information**: When the system creates an incident, Incident Manager now automatically collects information about the AWS resources involved in the incident. Incident Manager then adds this information to the **Related items** tab. | May 17, 2022 | | [Multi-runbook support](#doc-history) | Incident Manager now supports running multiple runbooks during an incident for the incident details page. | January 14, 2022 | | [Incident Manager launched in new AWS Regions](#doc-history) | Incident Manager is now available in these new Regions: us-west-1, sa-east-1, ap-northeast-2, ap-south-1, ca-central-1, eu-west-2, and eu-west-3. For more information about Incident Manager Regions and quotas, see the [AWS General Reference reference guide](https://docs.aws.amazon.com/general/latest/gr/incident-manager.html). | November 8, 2021 | | [Console engagement acknowledgement](#doc-history) | You can now acknowledge engagements directly from the Incident Manager console. | August 5, 2021 | | [Properties tab](#doc-history) | Incident Manager introduced a properties tab to the incident details page, providing more information about the incidents, the parent OpsItem, and the related post-incident analysis. | August 3, 2021 | | [Incident Manager launch](#doc-history) | Incident Manager is an incident management console designed to help users mitigate and recover from incidents affecting their AWS hosted applications. | May 10, 2021 |