I have published an InfoQ news post about the AWS team's approach to provision workflow orchestration as an integrated part of serverless applications:
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.
The Utoolity team is pleased to present
Identity Federation for AWS 2.13 –
this release adds a dialog for temporary AWS security credentials and provides an option to enable connector management by restricted administrators.
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.
I have published an InfoQ news post about the AWS team's solution for purely event-driven serverless workflows with manual steps and third-party integrations:
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.
The Utoolity team is pleased to present
Identity Federation for AWS 2.11 –
this release adds a single sign-on (SSO) enabled Bamboo web repository viewer for AWS CodeCommit, and adds an SSO enabled Jira remote issue link type for AWS resources in the AWS Management Console.
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.