aws ssm start-automation-execution
Initiates execution of an Automation document
Options
| Name | Description |
|---|---|
--document-name <string> | The name of the Systems Manager document to run. This can be a public document or a custom document. To run a shared document belonging to another account, specify the document ARN. For more information about how to use shared documents, see Using shared SSM documents in the AWS Systems Manager User Guide |
--document-version <string> | The version of the Automation document to use for this execution |
--parameters <map> | A key-value map of execution parameters, which match the declared parameters in the Automation document |
--client-token <string> | User-provided idempotency token. The token must be unique, is case insensitive, enforces the UUID format, and can't be reused |
--mode <string> | The execution mode of the automation. Valid modes include the following: Auto and Interactive. The default mode is Auto |
--target-parameter-name <string> | The name of the parameter used as the target resource for the rate-controlled execution. Required if you specify targets |
--targets <list> | A key-value mapping to target resources. Required if you specify TargetParameterName |
--target-maps <list> | A key-value mapping of document parameters to target resources. Both Targets and TargetMaps cannot be specified together |
--max-concurrency <string> | The maximum number of targets allowed to run this task in parallel. You can specify a number, such as 10, or a percentage, such as 10%. The default value is 10 |
--max-errors <string> | The number of errors that are allowed before the system stops running the automation on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops running the automation when the fourth error is received. If you specify 0, then the system stops running the automation on additional targets after the first error result is returned. If you run an automation on 50 resources and set max-errors to 10%, then the system stops running the automation on additional targets when the sixth error is received. Executions that are already running an automation when max-errors is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, set max-concurrency to 1 so the executions proceed one at a time |
--target-locations <list> | A location is a combination of AWS Regions and/or AWS accounts where you want to run the Automation. Use this action to start an Automation in multiple Regions and multiple accounts. For more information, see Running Automation workflows in multiple AWS Regions and accounts in the AWS Systems Manager User Guide |
--tags <list> | Optional metadata that you assign to a resource. You can specify a maximum of five tags for an automation. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag an automation to identify an environment or operating system. In this case, you could specify the following key name/value pairs: Key=environment,Value=test Key=OS,Value=Windows To add tags to an existing patch baseline, use the AddTagsToResource action |
--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 |