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:
|
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:
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" } |
You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are: