26 August 2015
Highlights
New tasks for AWS Lambda
You can now facilitate Amazon Web Service's new event-driven computing service AWS Lambda, which runs your code in response to events and automatically manages the compute resources for you - this is enabled by two new tasks:
Optionally specify a tag when running/starting an ECS Task
This adds the new ECS Task startedBy parameter, which is an optional tag specified when a task is started:
For example if you automatically trigger a task to run a batch process job, you could apply a unique identifier for that job to your task with the
startedBy
parameter. You can then identify which tasks belong to that job by filtering the results of a ListTasks call with thestartedBy
value.
- See New tasks for the Amazon EC2 Container Service (ECS) for the related former release notes.
Support for Enhanced Health Reporting, version 2 platform configurations and multiple WAR files in AWS Elastic Beanstalk tasks
The available solution stacks have been updated to include the latest versions, see the resp. announcements:
- Introducing Enhanced Application Health Monitoring
- Announcing support for multiple WAR files and new M4 instances
Updated solution stacks are always usable manually as soon as they are made available by AWS - this simply updates the user interface to include those for convenient selection.
Support for Java and Go applications
(As of release 2.8.2)
The available solution stacks have been updated to include the latest versions, see the resp. announcements:
Updated solution stacks are always usable manually as soon as they are made available by AWS - this simply updates the user interface to include those for convenient selection.
Details
This release addresses the following issues:
- Epics
- TAWS-484 - As a user, I want tasks to operate Lambda components so that I can facilitate event-driven computing
- Stories
- TAWS-485 - As a user, I want a task to create/entitle/invoke/update/delete a Lambda function so that I can perform deployments
- TAWS-486 - As a user, I want a task to create/update/delete a Lambda event source so that I can connect deployments
- Improvements
- TAWS-658 - Add ECS Task startedBy parameter
- TAWS-677- Update available Elastic Beanstalk solution stacks (as per 20150626)
- TAWS-685 - Remove outdated Elastic Beanstalk solution stacks
- TAWS-689 - Replace improvised ECS icon with official service icon
- TAWS-690 - Change task action radio buttons to select drop down
- TAWS-695 - Update available Elastic Beanstalk solution stacks (as per 20150803)
- TAWS-700 - Update available Elastic Beanstalk solution stacks (as per 20150811)
- TAWS-705 - Add inline dialog example for Elastic Beanstalk enhanced health monitoring option settings
- TAWS-712 - Surface support for additional CodeDeploy region ap-northeast-1
- TAWS-718 - Adjust task action labels to facilitate extended length
- Bugs
- Tasks
- TAWS-623 - Drop support for Bamboo 5.0
Release 2.8.2
This release addresses the following issues:
- Improvements
- TAWS-656 - Add ECS service state convergence timeout options
- TAWS-740 - Update available Elastic Beanstalk solution stacks (as per 20150925)
- TAWS-741 - Update available Elastic Beanstalk solution stacks (as per 20150928)
- TAWS-751 (UAA-111) - Add custom variable for container ID (UUID) in ECS Task tasks
- Bugs
- TAWS-657 - Amend/Fix ECS service state convergence failure conditions
Release 2.8.1
This release addresses the following issues:
- Improvements
- TAWS-728 - Add Elastic Beanstalk option to "Don't fail if application version already exists"
- TAWS-737 - Update available Elastic Beanstalk solution stacks (as per 20150819)