Using the Put Systems Manager Parameter action


You can use the Put Systems Manager Parameter action with the following integrations:


The Put Systems Manager Parameter 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:

1 2 3 4 5 6 7 8 9 10 11 12 13 { "Version": "2012-10-17", "Statement": [ { "Action": [ "ssm:PutParameter" ], "Resource": "*", "Effect": "Allow", "Sid": "SystemsManagerPutParameter" } ] }

 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 Put Systems Manager Parameter action:

Complete the following settings:



Specify the action parameters according to the following skeleton in JSON format – refer to ssm . put-parameter for details:

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

Event Data for Systems Manager Parameter

This is an opinionated example skeleton that works well for persisting custom event data from Atlassian products – refer to the PutParameter API action for details on these and other available fields.

Put Systems Manager Parameter skeleton - Atlassian Workflow Event

1 2 3 4 5 6 7 {   "Name": "/net/utoolity/automation-with-aws/events/$event.simpleName/timestamp",   "Description": "Automation with AWS: $event.simpleName with trace ID $event.traceId triggered at $event.timestamp.",   "Value": "$event.timestamp",   "Type": "String",   "Overwrite": true }


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)