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.

On this page:

1 Integrations
2 Requirements
3 Configuration
4 Entity Variables
5 Examples
6 How-to Articles
7 Frequently Asked Questions (FAQ)

Related pages:

Integrations

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

Requirements

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:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "ssm:StartAutomationExecution"
            ],
            "Resource": "*",
            "Effect": "Allow",
            "Sid": "SystemsManagerStartAutomationExecution"
        }
    ]
}

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

Configuration

To configure an Start Systems Manager Automation Execution action:

Complete the following settings:

Parameters

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

You can inject contextual variables into the remote action payload, refer to Entity Variables for details.

Event Data for Systems Manager Automation

This is an opinionated example skeleton to illustrate operating AWS resources from Atlassian products – refer to the StartAutomationExecution API action for details on these and other available fields.

Put Systems Manager Parameter skeleton - Atlassian Workflow Event

{
    "DocumentName": "AWS-PublishSNSNotification",
    "Parameters": {
        "TopicArn" : ["arn:aws:sns:eu-west-1:288727192237:aaws-quickstart-20170605-AutomationWithAWSQuickstartSNSTopic-12OFAKNZ2KKNR"],
"Message": ["Automation with AWS (start automation execution): $event.simpleName with trace ID $event.traceId triggered at $event.timestamp and published indirectly via Systems Manager Automation."]
    },
    "Mode": "Auto"
}

Entity Variables

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

Automation with AWS

Using the Start Systems Manager Automation Execution action

Integrations

Requirements

Configuration

Entity Variables

Examples

Filter by label

How-to Articles

Filter by label

Frequently Asked Questions (FAQ)