AWS incident-manager documentation change
Summary
Updated UI labels and workflow steps in Incident Manager setup guide. Changes include corrected capitalization ('Service access'), button label updates ('View permission details'), rephrased contact creation flow, and clarification of optional sections during preparation.
Security assessment
Changes appear to be UI/UX improvements and procedural clarifications rather than addressing specific security vulnerabilities. While Incident Manager relates to incident response, the modifications focus on workflow accuracy rather than introducing new security controls or addressing exploits.
Diff
diff --git a/incident-manager/latest/userguide/getting-started.md b/incident-manager/latest/userguide/getting-started.md index 2c8867c8e..20ca311b2 100644 --- a/incident-manager/latest/userguide/getting-started.md +++ b/incident-manager/latest/userguide/getting-started.md @@ -67 +67 @@ Tags are optional metadata that you assign to a resource. Tags allow you to cate - 6. (Optional) In the **Service Access** area, to activate the Findings feature, choose the **Create service role for findings in this account** check box. + 6. (Optional) In the **Service access** area, to activate the Findings feature, choose the **Create service role for findings in this account** check box. @@ -73 +73 @@ A _finding_ is information about a code deployment or infrastructure change that -To view information about the role to be created, choose **View permissions**. +To view information about the role to be created, choose **View permission details**. @@ -82,3 +82 @@ To learn more about replication sets and resiliency, see [Resilience in AWS Syst -###### Contacts (optional) - - 1. Choose **Create contact**. +###### Contacts (Optional during **Get prepared**) @@ -87,0 +86,2 @@ Incident Manager engages contacts during an incident. For more information about + 1. Choose **Create contact**. + @@ -102 +102 @@ Phone numbers must have 9–15 characters and start with `+` followed by the cou - 4. To create another contact channel, choose **Add a new contact channel**. We recommend defining at least two channels for each contact. + 4. To create another contact channel, choose **Add contact channel**. We recommend defining at least two channels for each contact. @@ -104 +104 @@ Phone numbers must have 9–15 characters and start with `+` followed by the cou - 5. In the **Engagement plan** area, do the following to define which channels to notify the contact through, and how long to wait for an acknowledgement through each channel. Select the contact channels to use to engage the contact during incidents. + 5. In the **Engagement plan** area, do the following to define which channels to notify the contact through, and how long to wait for an acknowledgement through each channel. @@ -108 +108 @@ Phone numbers must have 9–15 characters and start with `+` followed by the cou -We recommend defining at least two devices in the engagement plan. +We recommend defining at least two channels in the engagement plan. @@ -122 +122 @@ Tags are optional metadata that you assign to a resource. Tags allow you to cate - 7. To create the contact record and send activation codes to the defined contact channels, choose **Next**. + 7. To create the contact record and send activation codes to the defined contact channels, choose **Create**. @@ -128,3 +128 @@ You can generate new activation codes later if you're not able to enter the code - 9. Repeat step four until you have added all of your contacts to Incident Manager. - - 10. After all contacts are entered, choose **Finish**. + 9. To add additional contacts, choose **Create contact** and repeat the preceding steps. @@ -135 +133 @@ You can generate new activation codes later if you're not able to enter the code -###### (Optional) Escalation plans +###### (Optional during **Get prepared**) Escalation plans @@ -147 +145 @@ An escalation plan escalates through your contacts during an incident, ensuring - 1. For **Escalation channel** , choose contact channels to engage. + 1. For **Escalation channels** , choose contact channels to engage. @@ -166 +164,9 @@ Tags are optional metadata that you assign to a resource. Tags allow you to cate - 1. Choose **Create response plan**. Use the response plan to put together contacts and escalation plans you created. During this **Getting started** wizard, the following sections are optional, especially if this is your first time setting up a response plan: +###### Note + +You might need to return to the Incident Manager start page and choose **Prepare** to continue. + + 1. Choose **Create response plan**. + +Use the response plan to put together contacts and escalation plans you created. + +During this **Getting started** wizard, the following sections are optional, especially if this is your first time setting up a response plan: @@ -182 +188,3 @@ For information about adding these elements to response plans later, see [Prepar - 4. For **Title** , enter a title to help identify the type of incident that relates to this response plan. The value you specify is included in each incident's title. The alarm or event that started the incident is also added to the title. + 4. For **Title** , enter a title to help identify the type of incident that relates to this response plan. + +The value you specify is included in each incident's title. The alarm or event that started the incident is also added to the title. @@ -196 +204 @@ By default, Incident Manager automatically deduplicates multiple incidents creat - 8. (Optional) In the **Tags** area, add one or more tags to the response plan. A tag includes a key and, optionally, a value. + 8. (Optional) In the **Incident Tags** area, add one or more tags to the response plan. A tag includes a key and, optionally, a value.