Automation with AWS 1.4 Release Notes

20 September 2018

The Utoolity team is pleased to present Automation with AWS 1.4 – this release adds a new action for the AWS Systems Manager (SSM) Parameter Store to persist event data from Bamboo notifications and tasks, Jira workflow transitions, and Jira Service Desk automation rule executions as parameters in AWS where they can be either queried or trigger notifications and actions via Amazon CloudWatch Events in turn.

You can now use the Put Systems Manager Parameter action with all existing integrations for Bamboo, Jira, and Jira Service Desk.

Learn more and try it for free in:

On this page:

1 Highlights (Core)
- 1.1 Use the Put Systems Manager Parameter action to persist event data
- 1.2 Use CloudWatch Events to trigger notifications and actions for parameter updates
2 Resolved issues
- 2.1 Release 1.4.2
- 2.2 Release 1.4.1
- 2.3 Release 1.4.0

Highlights (Core)

Use the Put Systems Manager Parameter action to persist event data

You can now use the Put Systems Manager Parameter action to persist event data from Bamboo notifications and tasks, Jira workflow transitions, and Jira Service Desk automation rule executions into the AWS Systems Manager (SSM) Parameter Store for use in subsequent automation workflows. This allows you to decouple the capturing of secrets and configuration data from Jira Service Desk 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.

Use CloudWatch Events to trigger notifications and actions for parameter updates

Using this action can in turn trigger notifications and actions via all other services that are supported targets in CloudWatch Events (this is an alternative to using the Put CloudWatch Events action directly).

Resolved issues

Release 1.4.2

2018-12-20

This release addresses the following issues:

Core

Improvements
- AAWS-534 – Surface new AWS region EU (Stockholm) / eu-north-1
- AAWS-550 – Surface support for additional Step Functions region eu-west-3
- AAWS-551 – Surface support for additional Step Functions region sa-east-1

Release 1.4.1

2018-11-28

This release addresses the following issues:

Core

Improvements
- AAWS-516 – Surface new AWS region GovCloud (US-East) / us-gov-east-1

Release 1.4.0

2018-09-20

This release addresses the following issues:

Core

Stories
- AAWS-493 – As a user, I want to put a Systems Manager (SSM) parameter so that I can configure remote systems
Improvements
- AAWS-382 – Refactor Utoolity in-product messaging towards 'apps' and lowercase product names
- AAWS-463 – Add more granular CloudWatch rules source event patterns
- AAWS-478 – Surface support for additional Step Functions regions ap-northeast-2 and us-west-1
- AAWS-483 – Surface support for additional Step Functions region ap-south-1

Bamboo

Bugs
- AAWS-489 (UAA-357) – Log name of non existing region variable to ease analyzing configuration issues
Tasks
- AAWS-421 – Drop support for Bamboo 5.11
- AAWS-480 – Drop support for Bamboo 5.12
- AAWS-487 – Drop support for Bamboo 5.13

Jira

Tasks
- AAWS-379 – Drop support for Jira 7.1
- AAWS-429 – Drop support for Jira 7.2