Note: You are viewing the documentation for an older major version of the AWS CLI (version 1).

AWS CLI version 2, the latest major version of AWS CLI, is now stable and recommended for general use. To view this page for the AWS CLI version 2, click here. For more information see the AWS CLI version 2 installation instructions and migration guide.

[ aws . ssm-incidents ]



Updates the specified response plan.

See also: AWS API Documentation

See 'aws help' for descriptions of global parameters.


[--actions <value>]
--arn <value>
[--chat-channel <value>]
[--client-token <value>]
[--display-name <value>]
[--engagements <value>]
[--incident-template-dedupe-string <value>]
[--incident-template-impact <value>]
[--incident-template-notification-targets <value>]
[--incident-template-summary <value>]
[--incident-template-tags <value>]
[--incident-template-title <value>]
[--cli-input-json <value>]
[--generate-cli-skeleton <value>]


--actions (list)

The actions that this response plan takes at the beginning of an incident.


The action that starts at the beginning of an incident. The response plan defines the action.

ssmAutomation -> (structure)

The Systems Manager automation document to start as the runbook at the beginning of the incident.

documentName -> (string)

The automation document's name.

documentVersion -> (string)

The automation document's version to use when running.

dynamicParameters -> (map)

The key-value pair to resolve dynamic parameter values when processing a Systems Manager Automation runbook.

key -> (string)

value -> (structure)

The dynamic SSM parameter value.

variable -> (string)

Variable dynamic parameters. A parameter value is determined when an incident is created.

parameters -> (map)

The key-value pair parameters to use when running the automation document.

key -> (string)

value -> (list)


roleArn -> (string)

The Amazon Resource Name (ARN) of the role that the automation document will assume when running commands.

targetAccount -> (string)

The account that the automation document will be run in. This can be in either the management account or an application account.

Shorthand Syntax:

ssmAutomation={documentName=string,documentVersion=string,dynamicParameters={KeyName1={variable=string},KeyName2={variable=string}},parameters={KeyName1=[string,string],KeyName2=[string,string]},roleArn=string,targetAccount=string} ...

JSON Syntax:

    "ssmAutomation": {
      "documentName": "string",
      "documentVersion": "string",
      "dynamicParameters": {"string": {
      "parameters": {"string": ["string", ...]
      "roleArn": "string",

--arn (string)

The Amazon Resource Name (ARN) of the response plan.

--chat-channel (structure)

The Chatbot chat channel used for collaboration during an incident.

Use the empty structure to remove the chat channel from the response plan.

chatbotSns -> (list)

The Amazon SNS targets that Chatbot uses to notify the chat channel of updates to an incident. You can also make updates to the incident through the chat channel by using the Amazon SNS topics.


empty -> (structure)

Used to remove the chat channel from an incident record or response plan.

Shorthand Syntax:


JSON Syntax:

  "chatbotSns": ["string", ...],
  "empty": {


--client-token (string)

A token ensuring that the operation is called only once with the specified details.

--display-name (string)

The long format name of the response plan. The display name can't contain spaces.

--engagements (list)

The contacts and escalation plans that Incident Manager engages at the start of the incident.



"string" "string" ...

--incident-template-dedupe-string (string)

The string Incident Manager uses to prevent duplicate incidents from being created by the same incident in the same account.

--incident-template-impact (integer)

Defines the impact to the customers. Providing an impact overwrites the impact provided by a response plan.

Possible impacts:
  • 5 - Severe impact
  • 4 - High impact
  • 3 - Medium impact
  • 2 - Low impact
  • 1 - No impact

--incident-template-notification-targets (list)

The Amazon SNS targets that are notified when updates are made to an incident.


The SNS targets that are notified when updates are made to an incident.

snsTopicArn -> (string)

The Amazon Resource Name (ARN) of the SNS topic.

Shorthand Syntax:

snsTopicArn=string ...

JSON Syntax:

    "snsTopicArn": "string"

--incident-template-summary (string)

A brief summary of the incident. This typically contains what has happened, what's currently happening, and next steps.

--incident-template-tags (map)

Tags to apply to an incident when calling the StartIncident API action. To call this action, you must also have permission to call the TagResource API action for the incident record resource.

key -> (string)

value -> (string)

Shorthand Syntax:


JSON Syntax:

{"string": "string"

--incident-template-title (string)

The short format name of the incident. The title can't contain spaces.

--cli-input-json (string) Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

See 'aws help' for descriptions of global parameters.


To update a response plan

The following update-response-plan example removes a chat channel from the specified response plan.

aws ssm-incidents update-response-plan \
    --arn "arn:aws:ssm-incidents::111122223333:response-plan/Example-Response-Plan" \
    --chat-channel '{"empty":{}}'

This command produces no output.

For more information, see Incident preparation in the Incident Manager User Guide.