• The AWS Systems Manager CloudWatch Dashboard will no longer be available after April 30, 2026. Customers can continue to use Amazon CloudWatch console to view, create, and manage their Amazon CloudWatch dashboards, just as they do today. For more information, see [Amazon CloudWatch Dashboard documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html). # Visual design experience for Automation runbooks AWS Systems Manager Automation provides a low-code visual design experience that helps you create automation runbooks. The visual design experience provides a drag-and-drop interface with the option to add your own code so you can create and edit runbooks more easily. With the visual design experience, you can do the following: + Control conditional statements. + Control how input and output is filtered or transformed for each action. + Configure error handling. + Prototype new runbooks. + Use your prototype runbooks as the starting point for local development with the AWS Toolkit for Visual Studio Code. When you create or edit a runbook, you can access the visual design experience from the [Automation console](https://console.aws.amazon.com/systems-manager/automation/home?region=us-east-1#/). As you create a runbook, the visual design experience validates your work and auto-generates code. You can review the generated code, or export it for local development. When you're finished, you can save your runbook, run it, and examine the results in the Systems Manager Automation console. **Topics** + [Interface overview](visual-designer-interface-overview.md) + [ # Using the visual design experience ](visual-designer-use.md) + [Configure inputs and outputs](visual-designer-action-inputs-outputs.md) + [ # Error handling with the visual design experience ](visual-designer-error-handling.md) + [ # Tutorial: Create a runbook using the visual design experience ](visual-designer-tutorial.md) # Overview of the visual design experience interface Interface overview The visual design experience for Systems Manager Automation is a low-code visual workflow designer that helps you create automation runbooks. Get to know the visual design experience with an overview of the interface components: ![\[Visual design experience components\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_overview.png) + The **Actions** browser contains the **Actions**, **AWS APIs**, and **Runbooks** tabs. + The *canvas* is where you drag and drop actions into your workflow graph, change the order of actions, and select actions to configure or view. + The **Form** panel is where you can view and edit the properties of any action that you selected on the canvas. Select the **Content** toggle to view the YAML or JSON for your runbook, with the currently selected action highlighted. **Info** links open a panel with contextual information when you need help. These panels also include links to related topics in the Systems Manager Automation documentation. ## Actions browser From the **Actions** browser, you can select actions to drag and drop into your workflow graph. You can search all actions using the search field at the top of the **Actions** browser. The **Actions** browser contains the following tabs: + The **Actions** tab provides a list of automation actions that you can drag and drop into your runbook's workflow graph in the canvas. + The **AWS APIs** tab provides a list of AWS APIs that you can drag and drop into your runbook's workflow graph in the canvas. + The **Runbooks** tab provides several ready-to-use, reusable runbooks as building blocks that you can use for a variety of use cases. For example, you can use runbooks to perform common remediation tasks on Amazon EC2 instances in your workflow without having to re-create the same actions. ![\[Visual design experience actions browser\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_actions_multi_view.png) ## Canvas After you choose an action to add to your automation, drag it to the canvas and drop it into your workflow graph. You can also drag and drop actions to move them to different places in your runbook's workflow. If your workflow is complex, you might not be able to view all of it in the canvas panel. Use the controls at the top of the canvas to zoom in or out. To view different parts of a workflow, you can drag the workflow graph in the canvas. Drag an action from the **Actions** browser, and drop it into your runbook's workflow graph. A line shows where it will be placed in your workflow. To change the order of an action, you can drag it to a different place in your workflow. The new action has been added to your workflow, and its code is auto-generated. ![\[Visual design experience canvas\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_canvas.png) ## Form After you add an action to your runbook workflow, you can configure it to meet your use case. Choose the action that you want to configure, and you will see its parameters and options in the **Form** panel. You can also see the YAML or JSON code by choosing the **Content** toggle. The code associated with the action you have selected is highlighted. ![\[Visual design experience form panel\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_form.png) ![\[Visual design experience content panel\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_content.png) ## Keyboard shortcuts The visual design experience supports the keyboard shortcuts shown in the following table. | Keyboard shortcut | Function | | --- | --- | | Ctrl\$1Z | Undo the last operation. | | Ctrl\$1Shift\$1Z | Redo the last operation. | | Alt\$1C | Center the workflow in the canvas. | | Backspace | Remove all selected states. | | Delete | Remove all selected states. | | Ctrl\$1D | Duplicate the selected state. | # Using the visual design experience Learn to create, edit and run runbook workflows using the visual design experience. After your workflow is ready, you can save it or export it. You can also use the visual design experience for rapid prototyping. ## Create a runbook workflow 1. Sign in to the [Systems Manager Automation console](https://console.aws.amazon.com/systems-manager/automation/home?region=us-east-1#/). 1. Choose **Create runbook**. 1. In the **Name** box, enter a name for your runbook, for example, `MyNewRunbook`. 1. Next to the **Design** and **Code** toggle, select the pencil icon and enter a name for your runbook. You can now design a workflow for your new runbook. ## Design a runbook To design a runbook workflow using the visual design experience, you drag an automation action from the **Actions** browser into the canvas, placing it where you want it in your runbook's workflow. You can also re-order actions in your workflow by dragging them to a different location. As you drag an action onto the canvas, a line appears wherever you can drop the action in your workflow. After an action is dropped onto the canvas, its code is auto-generated and added inside your runbook's content. If you know the name of the action you want to add, use the search box at the top of the **Actions** browser to find the action. After you drop an action onto the canvas, configure it using the **Form** panel on the right. This panel contains the **General**, **Inputs**, **Outputs**, and **Configuration** tabs for each automation action or API action that you place on the canvas. For example, the **General** tab consists of the following sections: + The **Step name** identifies the step. Specify a unique value for the step name. + The **Description** helps you describe what the action is doing in your runbook's workflow. The **Inputs** tab contains fields that vary based on the action. For example, the `aws:executeScript` automation action consists of the following sections: + The **Runtime** is the language to use for running the provided script. + The **Handler** is the name of your function. You must ensure that the function defined in the handler has two parameters: `events` and `context`. The PowerShell runtime doesn't support this parameter. + The **Script** is an embedded script that you want to run during the workflow. + (Optional) The **Attachment** is for standalone scripts or .zip files that can be invoked by the action. This parameter is required for JSON runbooks. The **Outputs** tab helps you specify the values that you want to output from an action. You can reference output values in later actions of your workflow, or generate output from actions for logging purposes. Not all actions will have an **Outputs** tab because not all actions support outputs. For example, the `aws:pause` action doesn't support outputs. For actions that do support outputs, the **Outputs** tab consists of the following sections: + The **Name** is the name to be used for the output value. You can reference outputs in later actions of your workflow. + The **Selector** is a JSONPath expression string beginning with `"$."` that is used to select one or more components within a JSON element. + The **Type** is the data type for the output value. For example, a `String` or `Integer` data type. The **Configuration** tab contains properties and options that all automation actions can use. The action consists of the following sections: + The **Max attempts** property is the number of times an action retries if it fails. + The **Timeout seconds** property specifies the timeout value for an action. + The **Is critical** property determines if the action failure stops the entire automation. + The **Next step** property determines which action the automation goes to next in the runbook. + The **On failure** property determines which action the automation goes to next in the runbook if the action fails. + The **On cancel** property determines which action the automation goes to next in the runbook if the action is canceled by a user. To delete an action, you can use backspace, the toolbar above the canvas, or right-click and choose **Delete action**. As your workflow grows, it might not fit in the canvas. To help make the workflow fit in the canvas, try one of the following options: + Use the controls on the side panels to resize or close the panels. + Use the toolbar at the top of the canvas to zoom the workflow graph in or out. ## Update your runbook You can update an existing runbook workflow by creating a new version of your runbook. Updates to your runbooks can be made by using the visual design experience, or by editing the code directly. To update an existing runbook, use the following procedure: 1. Sign in to the [Systems Manager Automation console](https://console.aws.amazon.com/systems-manager/automation/home?region=us-east-1#/). 1. Choose the runbook that you want to update. 1. Choose **Create new version**. 1. The visual design experience has two panes: A code pane and a visual workflow pane. Choose **Design** in the visual workflow pane to edit your workflow with the visual design experience. When you're done, choose **Create new version** to save your changes and exit. 1. (Optional) Use the code pane to edit the runbook content in YAML or JSON. ## Export your runbook To export your runbook's workflow YAML or JSON code, and also a graph of your workflow, use the following procedure: 1. Choose your runbook in the **Documents** console. 1. Choose **Create new version**. 1. In the **Actions** dropdown, choose whether you want to export the graph or runbook, and which format you prefer. # Configuring inputs and outputs for your actions Configure inputs and outputs Each automation action responds based on input that it receives. In most cases, you then pass output to the subsequent actions. In the visual design experience, you can configure an action's input and output data in the **Inputs** and **Outputs** tabs of the **Form** panel. For detailed information about how to define and use output for automation actions, see [Using action outputs as inputs](automation-action-outputs-inputs.md). ## Provide input data for an action Each automation action has one or more inputs that you must provide a value for. The value you provide for an action's input is determined by the data type and format that's accepted by the action. For example, the `aws:sleep` actions requires an ISO 8601 formatted string value for the `Duration` input. Generally, you use actions in your runbook's workflow that return output that you want to use in subsequent actions. It's important to make sure your input values are correct to avoid errors in your runbook's workflow. Input values are also important because they determine whether the action returns the expected output. For example, when using the `aws:executeAwsApi` action, you want to make sure that you're providing the right value for the API operation. ## Define output data for an action Some automation actions return output after performing their defined operations. Actions that return output either have predefined outputs, or allow you to define the outputs yourself. For example, the `aws:createImage` action has predefined outputs that return an `ImageId` and `ImageState`. Comparatively, with the `aws:executeAwsApi` action, you can define the outputs you that want from the specified API operation. As a result, you can return one or more values from a single API operation to use in subsequent actions. Defining your own outputs for an automation action requires that you specify a name of the output, the data type, and the output value. To continue using the `aws:executeAwsApi` action as an example, let's say you're calling the `DescribeInstances` API operation from Amazon EC2. In this example, you want to return, or output, the `State` of an Amazon EC2 instance and branch your runbook's workflow based on the output. You choose to name the output **InstanceState**, and use the **String** data type. The process to define the actual value of the output differs, depending on the action. For example, if you're using the `aws:executeScript` action, you must use `return` statements in your functions to provide data to your outputs. With other actions like `aws:executeAwsApi`, `aws:waitForAwsResourceProperty`, and `aws:assertAwsResourceProperty`, a `Selector` is required. The `Selector`, or `PropertySelector` as some actions refer to it, is a JSONPath string that is used to process the JSON response from an API operation. It's important to understand how the JSON response object from an API operation is structured so you can select the correct value for your output. Using the `DescribeInstances` API operation mentioned earlier, see the following example JSON response: ``` { "reservationSet": { "item": { "reservationId": "r-1234567890abcdef0", "ownerId": 123456789012, "groupSet": "", "instancesSet": { "item": { "instanceId": "i-1234567890abcdef0", "imageId": "ami-bff32ccc", "instanceState": { "code": 16, "name": "running" }, "privateDnsName": "ip-192-168-1-88.eu-west-1.compute.internal", "dnsName": "ec2-54-194-252-215.eu-west-1.compute.amazonaws.com", "reason": "", "keyName": "my_keypair", "amiLaunchIndex": 0, "productCodes": "", "instanceType": "t2.micro", "launchTime": "2018-05-08T16:46:19.000Z", "placement": { "availabilityZone": "eu-west-1c", "groupName": "", "tenancy": "default" }, "monitoring": { "state": "disabled" }, "subnetId": "subnet-56f5f000", "vpcId": "vpc-11112222", "privateIpAddress": "192.168.1.88", "ipAddress": "54.194.252.215", "sourceDestCheck": true, "groupSet": { "item": { "groupId": "sg-e4076000", "groupName": "SecurityGroup1" } }, "architecture": "x86_64", "rootDeviceType": "ebs", "rootDeviceName": "/dev/xvda", "blockDeviceMapping": { "item": { "deviceName": "/dev/xvda", "ebs": { "volumeId": "vol-1234567890abcdef0", "status": "attached", "attachTime": "2015-12-22T10:44:09.000Z", "deleteOnTermination": true } } }, "virtualizationType": "hvm", "clientToken": "xMcwG14507example", "tagSet": { "item": { "key": "Name", "value": "Server_1" } }, "hypervisor": "xen", "networkInterfaceSet": { "item": { "networkInterfaceId": "eni-551ba000", "subnetId": "subnet-56f5f000", "vpcId": "vpc-11112222", "description": "Primary network interface", "ownerId": 123456789012, "status": "in-use", "macAddress": "02:dd:2c:5e:01:69", "privateIpAddress": "192.168.1.88", "privateDnsName": "ip-192-168-1-88.eu-west-1.compute.internal", "sourceDestCheck": true, "groupSet": { "item": { "groupId": "sg-e4076000", "groupName": "SecurityGroup1" } }, "attachment": { "attachmentId": "eni-attach-39697adc", "deviceIndex": 0, "status": "attached", "attachTime": "2018-05-08T16:46:19.000Z", "deleteOnTermination": true }, "association": { "publicIp": "54.194.252.215", "publicDnsName": "ec2-54-194-252-215.eu-west-1.compute.amazonaws.com", "ipOwnerId": "amazon" }, "privateIpAddressesSet": { "item": { "privateIpAddress": "192.168.1.88", "privateDnsName": "ip-192-168-1-88.eu-west-1.compute.internal", "primary": true, "association": { "publicIp": "54.194.252.215", "publicDnsName": "ec2-54-194-252-215.eu-west-1.compute.amazonaws.com", "ipOwnerId": "amazon" } } }, "ipv6AddressesSet": { "item": { "ipv6Address": "2001:db8:1234:1a2b::123" } } } }, "iamInstanceProfile": { "arn": "arn:aws:iam::123456789012:instance-profile/AdminRole", "id": "ABCAJEDNCAA64SSD123AB" }, "ebsOptimized": false, "cpuOptions": { "coreCount": 1, "threadsPerCore": 1 } } } } } } ``` In the JSON response object, the instance `State` is nested in an `Instances` object, which is nested in the `Reservations` object. To return the value of the instance `State`, use the following string for the `Selector` so the value can be used in our output: **\$1.Reservations[0].Instances[0].State.Name**. To reference an output value in subsequent actions of your runbook's workflow, the following format is used: `{{ StepName.NameOfOutput }}`. For example, **\$1\$1 GetInstanceState.InstanceState \$1\$1**. In the visual design experience, you can choose output values to use in subsequent actions using the dropdown for the input. When using outputs in subsequent actions, the data type of the output must match the data type for the input. In this example, the `InstanceState` output is a `String`. Therefore, to use the value in a subsequent action's input, the input must accept a `String`. # Error handling with the visual design experience By default, when an action reports an error, Automation stops the runbook's workflow entirely. This is because the default value for the `onFailure` property on all actions is `Abort`. You can configure how Automation handles errors in your runbook's workflow. Even if you have configured error handling, some errors might still cause an automation to fail. For more information, see [Troubleshooting Systems Manager Automation](automation-troubleshooting.md). In the visual design experience, you configure error handling in the **Configuration** panel. ![\[Error handling options\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_error_handling.png) ## Retry action on error To retry an action in case of an error, specify a value for the **Max attempts** property. The default value is 1. If you specify a value greater than 1, the action isn't considered to have failed until all of the retry attempts have failed. ## Timeouts You can configure a timeout for actions to set the maximum number of seconds your action can run before it fails. To configure a timeout, enter the number of seconds that your action should wait before the action fails in the **Timeout seconds** property. If the timeout is reached and the action has a value of `Max attempts` that is greater than 1, the step isn't considered to have timed out until the retries complete. ## Failed actions By default, when an action fails, Automation stops the runbook's workflow entirely. You can modify this behavior by specifying an alternative value for the **On failure** property of the actions in your runbook. If you want the workflow to continue to the next step in the runbook, choose **Continue**. If you want the workflow to jump to a different subsequent step in the runbook, choose **Step** and then enter the name of the step. ## Canceled actions By default, when an action is canceled by a user, Automation stops the runbook's workflow entirely. You can modify this behavior by specifying an alternative value for the **On cancel** property of the actions in your runbook. If you want the workflow to jump to a different subsequent step in the runbook, choose **Step** and then enter the name of the step. ## Critical actions You can designate an action as *critical*, meaning it determines the overall reporting status of your automation. If a step with this designation fails, Automation reports the final status as `Failed` regardless of the success of other actions. To configure an action as critical, leave the default value as **True** for the **Is critical** property. ## Ending actions The **Is end** property stops an automation at the end of the specified action. The default value for this property is `false`. If you configure this property for an action, the automation stops whether the action succeeds or fails. This property is most often used with `aws:branch` actions to handle unexpected or undefined input values. The following example shows a runbook that is expecting an instance state of either `running`, `stopping`, or `stopped`. If an instance is in a different state, the automation ends. ![\[Visual design experience is end example\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_is_end_example.png) # Tutorial: Create a runbook using the visual design experience In this tutorial, you will learn the basics of working with the visual design experience provided by Systems Manager Automation. In the visual design experience, you can create a runbook that uses multiple actions. You use the drag and drop feature to arrange actions on the canvas. You also search for, select, and configure these actions. Then, you can view the auto-generated YAML code for your runbook's workflow, exit the visual design experience, run the runbook, and review the execution details. This tutorial also shows you how to update the runbook and view the new version. At the end of the tutorial, you perform a clean-up step and delete your runbook. After you complete this tutorial, you'll know how to use the visual design experience to create a runbook. You'll also know how to update, run, and delete your runbook. **Note** Before you start this tutorial, make sure to complete [Setting up Automation](automation-setup.md). **Topics** + [ ## Step 1: Navigate to the visual design experience ](#navigate-console) + [ ## Step 2: Create a workflow ](#create-workflow) + [ ## Step 3: Review the auto-generated code ](#view-generated-code) + [ ## Step 4: Run your new runbook ](#use-tutorial-runbook) + [ ## Step 5: Clean up ](#cleanup-tutorial-runbook) ## Step 1: Navigate to the visual design experience 1. Sign in to the [Systems Manager Automation console](https://console.aws.amazon.com/systems-manager/automation/home?region=us-east-1#/). 1. Choose **Create automation runbook**. ## Step 2: Create a workflow In the visual design experience, a workflow is a graphical representation of your runbook on the canvas. You can use the visual design experience to define, configure, and examine the individual actions of your runbook. **To create a workflow** 1. Next to the **Design** and **Code** toggle, select the pencil icon and enter a name for your runbook. For this tutorial, enter **VisualDesignExperienceTutorial**. ![\[Visual design experience name your runbook\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_tutorial_name.png) 1. In the **Document attributes** section of the **Form** panel, expand the **Input parameters** dropdown, and select **Add a parameter**. 1. In the **Parameter name** field, enter **InstanceId**. 1. In the **Type** dropdown, choose **AWS::EC2::Instance**. 1. Select the **Required** toggle. ![\[Create a parameter for your runbook\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_actions_tutorial_parameter.png) 1. In the **AWS APIs** browser, enter **DescribeInstances** in the search bar. 1. Drag an **Amazon EC2 – DescribeInstances** action to the empty canvas. 1. For **Step name**, enter a value. For this tutorial, you can use the name **GetInstanceState**. ![\[Choose an Amazon EC2 describe instances API action.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_tutorial_api_action.png) 1. Expand the **Additional inputs** dropdown, and in the **Input name** field, enter **InstanceIds**. 1. Choose the **Inputs** tab. 1. In the **Input value** field, choose the **InstanceId** document input. This references the value of the input parameter that you created at the beginning of the procedure. Since the **InstanceIds** input for the `DescribeInstances` action accepts `StringList` values, you must wrap the **InstanceId** input in square brackets. The YAML for the **Input value** should match the following: **['\$1\$1 InstanceId \$1\$1']**. 1. In the **Outputs** tab, select **Add an output** and enter **InstanceState** in the **Name** field. 1. In the **Selector** field, enter **\$1.Reservations[0].Instances[0].State.Name**. 1. In the **Type** dropdown, choose **String**. 1. Drag a **Branch** action from the **Actions** browser, and drop it below the **`GetInstanceState`** step. 1. For **Step name**, enter a value. For this tutorial, use the name `BranchOnInstanceState`. To define the branching logic, do the following: 1. Choose the **`Branch`** state on the canvas. Then, under **Inputs** and **Choices**, select the pencil icon to edit **Rule \$11**. 1. Choose **Add conditions**. 1. In the **Conditions for rule \$11** dialog box, choose the **GetInstanceState.InstanceState** step output from the **Variable** dropdown. 1. For **Operator**, choose **is equal to**. 1. For **Value**, choose **String** from the dropdown list. Enter **stopped**. ![\[Define a condition for a branch action.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_tutorial_condition.png) 1. Select **Save conditions**. 1. Choose **Add new choice rule**. 1. Choose **Add conditions** for **Rule \$12**. 1. In the **Conditions for rule \$12** dialog box, choose the **GetInstanceState.InstanceState** step output from the **Variable** dropdown. 1. For **Operator**, choose **is equal to**. 1. For **Value**, choose **String** from the dropdown list. Enter **stopping**. 1. Select **Save conditions**. 1. Choose **Add new choice rule**. 1. For **Rule \$13**, choose **Add conditions**. 1. In the **Conditions for rule \$13** dialog box, choose the **GetInstanceState.InstanceState** step output from the **Variable** dropdown. 1. For **Operator**, choose **is equal to**. 1. For **Value**, choose **String** from the dropdown list. Enter **running**. 1. Select **Save conditions**. 1. In the **Default rule**, choose **Go to end** for the **Default step**. 1. Drag a **Change an instance state** action to the empty **Drag action here** box under the **\$1\$1 GetInstanceState.InstanceState \$1\$1 == "stopped"** condition. 1. For the **Step name**, enter **StartInstance**. 1. In the **Inputs** tab, under **Instance IDs**, choose the **InstanceId** document input value from the dropdown. 1. For the **Desired state**, specify **`running`**. 1. Drag a **Wait on AWS resource** action to the empty **Drag action here** box under the **\$1\$1 GetInstanceState.InstanceState \$1\$1 == "stopping"** condition. 1. For **Step name**, enter a value. For this tutorial, use the name `WaitForInstanceStop`. 1. For the **Service** field, choose **Amazon EC2**. 1. For the **API** field, choose **DescribeInstances**. 1. For the **Property selector** field, enter **\$1.Reservations[0].Instances[0].State.Name**. 1. For the **Desired values** parameter, enter **`["stopped"]`**. 1. In the **Configuration** tab of the **WaitForInstanceStop** action, choose **StartInstance** from the **Next step** dropdown. 1. Drag a **Run command on instances** action to the empty **Drag action here** box under the **\$1\$1 GetInstanceState.InstanceState \$1\$1 == "running"** condition. 1. For the **Step name**, enter **SayHello**. 1. In the **Inputs** tab, enter **AWS-RunShellScript** for the **Document name** parameter. 1. For **InstanceIds**, choose the **InstanceId** document input value from the dropdown. 1. Expand the **Additional inputs** dropdown, and in the **Input name** dropdown, choose **Parameters**. 1. In the **Input value** field, enter **`{"commands": "echo 'Hello World'"}`**. 1. Review the completed runbook in the canvas and select **Create runbook** to save the tutorial runbook. ![\[Review and create the runbook.\]](http://docs.aws.amazon.com/systems-manager/latest/userguide/images/visual_designer_tutorial_complete.png) ## Step 3: Review the auto-generated code As you drag and drop actions from the **Actions** browser onto the canvas, the visual design experience automatically composes the YAML or JSON content of your runbook in real-time. You can view and edit this code. To view the auto-generated code, select **Code** for the **Design** and **Code** toggle. ## Step 4: Run your new runbook After creating your runbook, you can run the automation. **To run your new automation runbook** 1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/). 1. In the navigation pane, choose **Automation**, and then choose **Execute automation**. 1. In the **Automation document** list, choose a runbook. Choose one or more options in the **Document categories** pane to filter SSM documents according to their purpose. To view a runbook that you own, choose the **Owned by me** tab. To view a runbook that is shared with your account, choose the **Shared with me** tab. To view all runbooks, choose the **All documents** tab. **Note** You can view information about a runbook by choosing the runbook name. 1. In the **Document details** section, verify that **Document version** is set to the version that you want to run. The system includes the following version options: + **Default version at runtime** – Choose this option if the Automation runbook is updated periodically and a new default version is assigned. + **Latest version at runtime** – Choose this option if the Automation runbook is updated periodically, and you want to run the version that was most recently updated. + **1 (Default)** – Choose this option to run the first version of the document, which is the default. 1. Choose **Next**. 1. In the **Execute automation runbook** section, choose **Simple execution**. 1. In the **Input parameters** section, specify the required inputs. Optionally, you can choose an IAM service role from the **AutomationAssumeRole** list. 1. (Optional) Choose an Amazon CloudWatch alarm to apply to your automation for monitoring. To attach a CloudWatch alarm to your automation, the IAM principal that starts the automation must have permission for the `iam:createServiceLinkedRole` action. For more information about CloudWatch alarms, see [Using Amazon CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html). If your alarm activates, the automation is stopped. If you use AWS CloudTrail, you will see the API call in your trail. 1. Choose **Execute**. ## Step 5: Clean up **To delete your runbook** 1. Open the AWS Systems Manager console at [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/). 1. In the navigation pane, choose **Documents**. 1. Select the **Owned by me** tab. 1. Locate the **VisualDesignExperienceTutorial** runbook. 1. Select the button on the document card page, and then choose **Delete document** from the **Actions** dropdown.