Automation with AWS Release Notes

The Utoolity team is pleased to present Automation with AWS 2.2 – this release migrates to the AWS SDK for Java 2.x and surfaces 5 new AWS regions in turn.

You can now visually select all AWS regions supported by the AWS SDK for Java 2.x, including the more recent Asia Pacific regions Malaysia, Thailand, Taipei, and New Zealand, as well as Mexico Central.

The Utoolity team is pleased to present Automation with AWS 1.13 – this release migrates to the AWS SDK for Java 2.x and surfaces 5 new AWS regions in turn.

You can now visually select all AWS regions supported by the AWS SDK for Java 2.x, including the more recent Asia Pacific regions Malaysia, Thailand, Taipei, and New Zealand, as well as Mexico Central.

The Utoolity team is pleased to present Automation with AWS 2.1 – this release adds support for providing AWS security credentials to actions and conditions via IAM role for EKS service accounts (IRSA).

If you have provisioned your Atlassian workloads on the Amazon Elastic Kubernetes Service (Amazon EKS), you can now enable the IAM role for EKS service accounts credentials provider to benefit from the convenience and flexibility of providing temporary AWS security credentials to actions and conditions via IAM roles for service accounts.

The Utoolity team is pleased to present Automation with AWS 1.12 – this release adds support for providing AWS security credentials to actions and conditions via IAM role for EKS service accounts (IRSA).

If you have provisioned your Atlassian workloads on the Amazon Elastic Kubernetes Service (Amazon EKS), you can now enable the IAM role for EKS service accounts credentials provider to benefit from the convenience and flexibility of providing temporary AWS security credentials to actions and conditions via IAM roles for service accounts.

The Utoolity team is pleased to present Automation with AWS 2.0 – this release adds support for the AWS CodeArtifact Credentials Variables task, adds a REST API for temporary AWS CodeArtifact credentials (authentication tokens), and upgrades the app to Atlassian Data Center Platform 7 (Jira 10 and Bamboo 10).

You can now use the /wiki/spaces/IFAWS/pages/3852173313 in Bamboo to provide temporary AWS CodeArtifact authentication tokens to other tools by injecting them via variables into AWS unaware tasks like the Bamboo Script task, retrieve AWS CodeArtifact authentication tokens via the REST API, and you can use the app with Jira 10.0.x and Bamboo 10.0.x.

The Utoolity team is pleased to present Automation with AWS 1.11 – this release adds support for the AWS CodeArtifact Credentials Variables task in Bamboo, and adds a REST API for temporary AWS CodeArtifact credentials (authentication tokens).

You can now use the /wiki/spaces/IFAWS/pages/3852173313 in Bamboo to provide temporary AWS CodeArtifact authentication tokens to other tools by injecting them via variables into AWS unaware tasks like the Bamboo Script task, and retrieve AWS CodeArtifact authentication tokens via the REST API.

The Utoolity team is pleased to present Automation with AWS 1.10 – this release adds full compatibility with Bamboo Data Center and adds an integration to start synchronous AWS Step Functions Express workflow executions.

You can now use the app with non-clustered and clustered Bamboo Data Center deployments to gain the flexibility and administrative control to manage mission-critical Bamboo sites, and you can run actions and evaluate conditions by starting synchronous Express workflow executions via the /wiki/spaces/UAAWS/pages/2913599489.

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.

The Utoolity team is pleased to present Automation with AWS 1.8 – this release introduces remote conditions with AWS for Jira Service Desk automation, Jira workflow transitions, and Bamboo builds and deployments.

You can now use the Invoke Lambda Function action to evaluate remote conditions so that you can control Jira Service Desk 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.

The Utoolity team is pleased to present Automation with AWS 1.7 – this release rebrands the existing Put CloudWatch Events action to also support Amazon EventBridge to relay, match and route Atlassian workflow events to AWS where they can be processed by one or more target services and adds support for managed IAM policies.

You can now use the Put EventBridge/CloudWatch Events action with all existing integrations for Bamboo, Jira and Jira Service Desk, and you can use managed IAM policies in addition to (or replacing) the former inline IAM policies to consolidate IAM policy management.

The Utoolity team is pleased to present Automation with AWS 1.6 – this release adds a new action for AWS Systems Manager Automation to manage AWS resources from Bamboo notifications, Jira workflow transitions, and Jira Service Desk automation rule executions.

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

The Utoolity team is pleased to present Automation with AWS 1.5 – this release adds a new action for the Amazon Simple Queue Service (SQS) to relay event data from Bamboo notifications, Jira workflow transitions, and Jira Service Desk automation rule executions via AWS so that they can be processed by other services.

You can now use the Send SQS Message action with all existing integrations for Bamboo, Jira, and Jira Service Desk.

This release also addresses a breaking API/SPI change within Jira Service Desk 4 by providing separate artifacts for Jira 7.x and Jira 8.x
compatibility.

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.

The Utoolity team is pleased to present Automation with AWS 1.3 – this release adds a new action for Amazon CloudWatch Events to relay, match and route Atlassian workflow events to AWS where they can be processed by one or more target services, and adds plan, result and deployment entity variables to ease Bamboo notification payload composition.

You can now use the Put CloudWatch Events action with all existing integrations for Bamboo, Jira and Jira Service Desk, and you can inject additional entity variables into Bamboo notification payloads.

The Utoolity team is pleased to present Automation with AWS 1.2 – this release adds a Bamboo task to run remote actions with AWS from Bamboo jobs in build and deployment projects, and adds utility functions to ease JSON escaping, URL encoding, and Base64 encoding.

You can now use the Automate with AWS task with all available AWS actions, and you can compose action payloads with utility functions.

The Utoolity team is pleased to present Automation with AWS 1.1 – this release adds a new action for AWS Step Functions state machines to enable coordination of components of distributed applications and microservices using visual workflows.

You can now use the Start Step Functions Execution action with all existing integrations for Bamboo, JIRA and JIRA Service Desk.

The Utoolity team is pleased to present Automation with AWS 1.0 – this release adds a Bamboo notification recipient, a JIRA post function and a JIRA Service Desk then action to run remote actions with AWS from workflows, and adds actions for AWS Lambda functions and Amazon Simple Notification Service (SNS) topics.

You can use the Invoke Lambda Function and Publish SNS Message actions with all integrations for Bamboo and JIRA.