I have published an InfoQ news post about the AWS team's serverless solution for obsoleting custom code to "capture, transform, buffer, compress and upload data" en route to destinations:
I have published an InfoQ news post about the AWS team's serverless solution for orchestrating high-volume, short duration microservices behind Amazon API Gateway:
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.
I have published an InfoQ news post about the AWS team's solution for integrating third-party destinations for Amazon Kinesis Data Firehose:
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
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
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.
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, Jira workflow transitions, and Jira Service Desk automation rule executions to AWS where they can be either queried or trigger notifications and actions via Amazon CloudWatch Events in turn.
I have published an InfoQ news post about the AWS team's efforts to accelerate the evolution of CloudFormation's built-in serverless support:
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.
I have published an InfoQ news post about the AWS team's efforts to establish a discovery and distribution platform for serverless solutions:
I have published an InfoQ news post about AWS's after the fact addition of automation capabilities for CloudWatch Dashboards:
I have published an InfoQ news post about the AWS team's efforts to ease cross-account tracking of CloudWatch events: