Automation with AWS 1.9 Release Notes

30 November 2020

The Utoolity team is pleased to present Automation with AWS 1.9 – this release adds an action to get parameters from the AWS Systems Manager Parameter Store to evaluate remote conditions and inject remote configuration data and secrets. It also adds an IAM role for EC2/ECS credentials provider and introduces namespace and scope handling for generated Bamboo variables.

You can now use the Get Systems Manager Parameter action to evaluate remote conditions so that you can control Jira Service Management automation rules via the Automate with AWS if condition, control Jira workflow transitions via the Automate with AWS workflow condition and Automate with AWS workflow validator, and fail or succeed Bamboo builds and deployments via the Automate with AWS task. You can also use this action to inject remote configuration data and secrets stored as secure parameters in the AWS Systems Manager Parameter Store, or stored as secrets within AWS Secrets Manager. Further, you can now provide AWS security credentials via an IAM role for EC2/ECS when you run your Atlassian products on Amazon EC2, Amazon ECS, or AWS Fargate, and you can adjust the namespace and scope of generated Bamboo variables.

Highlights (Core)

Evaluate remote conditions with the Get Systems Manager Parameter action

You can now use the Get Systems Manager Parameter action in applicable integrations to evaluate arbitrary remote conditions by persisting a JSON result shape that adheres to the action response format schema:

{
        'result': false,
        'errorMessage': "Workflow transition blocked due to a prerequisite condition being false"
}

This allows you to use an event-based architecture to decouple condition evaluation in AWS from condition evaluation in Atlassian to ensure that any prerequisites for your workflows are automatically checked right before dependent steps are initiated, thereby reducing cost and latency over using the Invoke Lambda Function action to synchronously call AWS services and third-party REST APIs at evaluation time.

Currently supported integrations are the Jira Service Management Automate with AWS if condition, the Jira Automate with AWS workflow condition and Automate with AWS workflow validator, and the Bamboo Automate with AWS task.

Inject remote configuration data and secrets with the Get Systems Manager Parameter action

You can now use the Get Systems Manager Parameter action in applicable integrations to inject arbitrary remote configuration data and secrets via the Systems Manager Parameter Store:

This allows you to maintain configuration data and regular secrets as (secure) parameters in the Systems Manager Parameter Store, and optionally maintain secrets in AWS Secrets Manager when you require more advanced secret lifecycle management.

Parameter Store vs. Secrets Manager

Depending on your use case and security governance requirements, you can store secrets as Parameter Store parameters of type SecureString, or as actual Secrets Manager secrets as outlined in Referencing AWS Secrets Manager secrets from Parameter Store parameters. The following articles provide a comparison between the two services:

Currently supported integrations are the Bamboo Automate with AWS task.

Highlights (Bamboo)

Adjust generated Bamboo variable namespace and scope

Similar to the Inject Bamboo variables task that has been included with Bamboo as of release 6.7, you can now specify the namespace and scope for Bamboo variables generated by the Automate with AWS task to enable more flexible build orchestration. You can now pass a variable between stages, pass a variable from a plan to a deployment project, and you can use multiple tasks within the same job without overriding variables from preceding tasks by adjusting the namespace. The task defaults to the preceding behavior with local scope and a custom.aws namespace so that this remains an opt-in choice for advanced use cases.

Resolved issues

Release 1.9.2

2021-05-18

This release addresses the following issues:

Core

  • Improvements

    • AAWS-876 – Update Identity Federation for AWS dependency to 2.14.2

Bamboo

  • Bugs

    • AAWS-877 – Fix erroneous script tag usage in Bamboo tasks

Release 1.9.1

2021-05-18

This release addresses the following issues:

Core

  • Improvements

    • AAWS-845 – Surface new AWS region Asia Pacific (Osaka) / ap-northeast-3

    • AAWS-850 – Update Identity Federation for AWS dependency to 2.14.1

Release 1.9.0

2020-11-30

This release addresses the following issues:

Core

  • Stories

    • AAWS-731 – As a user, I want to get a Systems Manager (SSM) parameter so that I can inject remote data

    • AAWS-739 – As a user, I want to get a Systems Manager (SSM) parameter so that I can check remote conditions

Jira

  • Tasks

    • AAWS-759 – Drop support for Jira 7.9

    • AAWS-764 – Drop support for Jira 7.10

    • AAWS-802 – Drop support for Jira 7.11

    • AAWS-805 – Drop support for Jira 7.12

Bamboo

  • Stories

    • AAWS-814 – As a user, I want to be in control of variable namespace and scope so that I gain simplified plan composition

  • Tasks

    • AAWS-760 – Drop support for Bamboo 6.5

    • AAWS-799 – Drop support for Bamboo 6.6

Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.