Using the Put Systems Manager Parameter action

Use the Put Systems Manager Parameter action to persist event data from Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions into the AWS Systems Manager Parameter Store that you can then consume in subsequent automation workflows. This allows you to decouple the capturing of secrets and configuration data from Jira Service Management request approvals, Jira issue edits or Bamboo plan executions from the decision to trigger subsequent automation by one or more target services:

AWS Systems Manager Parameter Store provides secure, hierarchical storage for configuration data management and secrets management. You can store data such as passwords, database strings, and license codes as parameter values. You can store values as plain text or encrypted data. You can then reference values by using the unique name that you specified when you created the parameter. [...] Parameter Store is offered at no additional charge.

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 Put Systems Manager Parameter action with the following integrations:

Requirements

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:

{
    "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.

Configuration

To configure an Put Systems Manager Parameter action:

Complete the following settings:

Parameters

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

{
  "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:

Automation with AWS

Using the Put Systems Manager Parameter action

Integrations

Requirements

Configuration

Entity Variables

Examples

Filter by label

How-to Articles

Filter by label

Frequently Asked Questions (FAQ)