Using the Start Systems Manager Automation Execution action

Use the Start Systems Manager Automation Execution action from Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions to simplify common maintenance and deployment tasks of Amazon EC2 instances and other AWS resources via AWS Systems Manager Automation. Automation enables you to do the following.: 

  • Build Automation workflows to configure and manage instances and AWS resources.

  • Create custom workflows or use pre-defined workflows maintained by AWS.

  • Receive notifications about Automation tasks and workflows by using Amazon CloudWatch Events.

  • Monitor Automation progress and execution details by using the Amazon EC2 or the AWS Systems Manager console.


You can use the Start Systems Manager Automation Execution action with the following integrations:


The Start Systems Manager Automation Execution action requires sufficient IAM permissions - an adequate IAM policy similar to the one provisioned by the Automation with AWS (Core) CloudFormation template might look as follows:

(lightbulb) Refer to Using Identity-Based Policies (IAM Policies) for AWS Systems Manager for details on how to create more granular/secure policies.


To configure an Start Systems Manager Automation Execution action:

  1. Complete the following settings:


    Specify the action parameters according to the following skeleton in JSON format – refer to ssm . start-automation-execution for details:

Entity Variables

You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are:


How-to Articles

Frequently Asked Questions (FAQ)