18 February 2016
The Utoolity team is pleased to present Tasks for AWS 2.10 – this release adds an Amazon ECR Credentials Variables task to Bamboo for providing temporary Amazon EC2 Container Registry authentication credentials to other tools by injecting them via variables into AWS unaware tasks like the Bamboo Docker task, supports additional deployment options for the Amazon EC2 Container Service (ECS), and adds support for assuming another IAM role from EC2 instance profile credentials used by an Elastic Bamboo agent.
If you are using Bamboo remote agents, please review the Tasks for AWS 2.10 Upgrade Notes for important information about this release.
Highlights
New task to provide Amazon EC2 Container Registry (ECR) Credentials Variables
Use the Amazon ECR Credentials Variables task in Bamboo to provide temporary Amazon EC2 Container Registry (ECR) authentication credentials for other tools by injecting them into AWS unaware tasks like the Bamboo Docker task.
- This task is provided by Identity Federation for AWS (Bamboo), which is bundled and free for Tasks for AWS licensees, see the Licensing & Purchasing FAQ for details.
Use Amazon ECR Credentials with Bamboo Docker task
The most frequent use case for the Amazon ECR Credentials Variables task is to enable the built-in Bamboo Docker task to push images to an Amazon ECR repository - refer to How to push a Docker image to a repository in your Amazon ECR registry with the Bamboo Docker task for details.
Additional deployment options for the Amazon EC2 Container Service (ECS)
You can now use the recently introduced additional deployment parameters when creating or updating a service with the Amazon ECS Service task:
- Minimum Healthy Percent - specify a lower limit on the number of running tasks during a deployment (to deploy without using additional cluster capacity)
- Maximum Percent - specify an upper limit on the number of running tasks during a deployment (to define the deployment batch size)
The tasks to deploy and manage Docker containers with the Amazon EC2 Container Service (ECS) have been introduced in Tasks for AWS 2.7.
Support for assuming another IAM Role from EC2 Instance Profile credentials
The IAM Role for EC2 (Agent) option in all tasks for Bamboo now supports assuming another IAM role from the EC2 instance profile credentials - this enables various scenarios, notably switching to roles accross your own AWS accounts and third-party.AWS accounts (cross-account IAM roles).
Support for t2.nano EC2 instances, Docker 1.9 and the Amazon EC2 Container Registry (ECR) in AWS Elastic Beanstalk tasks
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:
- Stories
- TAWS-846 (UAA-74) - As a user, I want to let an instance role assume another role so that EC2 instances can be leveraged for cross-account IAM usage
- Improvements
- TAWS-521 - Add inline dialog with sample stack policies and help pointers
- TAWS-816 - Update AWS Elastic Beanstalk icons
- TAWS-857 - Update available Elastic Beanstalk solution stacks (as per 2016-01-11)
- TAWS-858 - Surface additional AWS region ap-northeast-2
- TAWS-859 - Surface support for additional ECS regions ap-southeast-1 and eu-central-1
- TAWS-860 - Add additional ECS deployment options
- TAWS-864 - Surface support for additional CodeDeploy region us-west-1
- TAWS-887 (UAA-142) - Adjust OpsWorks resource related wording to avoid confusion with EC2 concepts
- TAWS-893 - Update available Elastic Beanstalk solution stacks (as per 2016-02-11)
- Bugs
- TAWS-856 - Update available Elastic Beanstalk solution stacks (as per 2015-12-18)
- TAWS-885 - Fix status monitoring loops potentially hanging after error logging
- TAWS-889 (UAA-145) - Fix ElasticBeanstalk solution stack field incorrectly being marked as required on update edit screen
- TAWS-891 - Unify/Fix validation error message parentheses and escaping
- Tasks
- TAWS-832 - Drop support for Bamboo 5.3
Release 2.10.3
2016-04-12
This release addresses the following issues:
- Improvements
- TAWS-513 (UAA-93) - Improve API compatibility/coverage of EBS Snapshot and EC2 Image tasks
- TAWS-900 - Ignore errors for deregistered images on EC2 Image backup/delete actions
- TAWS-918 - Surface support for additional CodeDeploy region sa-east-1
- TAWS-919 - Surface support for additional Lambda region eu-central-1
- TAWS-938 - Adjust handling of explicit resource ID entry on EC2 tasks
- TAWS-950 (UAA-152) - Add UI support for surfacing/copying an AWS connector ID
- TAWS-952 - Add support for Lambda Node.js 4.3 runtime
- TAWS-953 - Update available Elastic Beanstalk solution stacks (as per 2016-04-07)
- TAWS-954 - Increase supported Elastic Beanstalk environment name length from 23 to 40
- Bugs
- TAWS-942 - Fix EC2 tasks partially not accounting for more than 1000 resources
- TAWS-945 (UAA-159) - Fix/Add generation of missing Bamboo variables in ECS task actions
Release 2.10.2
2016-03-16
This release addresses the following issues:
- Bugs
- TAWS-914 - Update available Elastic Beanstalk solution stacks (as per 2016-02-26)
- TAWS-920 (UAA-151) - Fix ClassNotFoundException when validating multiple CloudFormation templates on remote agents
Release 2.10.1
2016-02-26
This release addresses the following issues:
- Improvements
- TAWS-892 - Add Virtual Private Cloud (VPC) support to Lambda Function task
- TAWS-901 (UAA-143) - Add validation of all CloudFormation templates with a specified S3 virtual directory prefix
- Bugs
- TAWS-896 - Fix typo in ECS Service deployment configuration description
- TAWS-910 - Fix template source examples inline dialog not showing on CloudFormation Stack update action
- TAWS-912 - Fix AWS partition-global endpoint being available for region selection in S3 Object task