AWS incident-manager documentation change
Summary
Fixed URL formatting in runbook parameters section (added double slash)
Security assessment
This change only corrects a URL path formatting issue without altering security content or functionality.
Diff
diff --git a/incident-manager/latest/userguide/doc-history.md b/incident-manager/latest/userguide/doc-history.md index 000584d2e..93b94f428 100644 --- a//incident-manager/latest/userguide/doc-history.md +++ b//incident-manager/latest/userguide/doc-history.md @@ -10,0 +11,2 @@ Change| Description| Date +AWS Systems Manager Incident Manager published migration docs| 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| 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 @@ -24 +26 @@ Updated lists of integrations with Incident Manager| The topic [Product and serv -Integration with AWS Trusted Advisor| 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 +Integration with AWS Trusted Advisor| 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 @@ -58 +60 @@ Multiple feature improvements to enhance incident creation and remediation| Inci - * **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 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).