Tasks for AWS 2.13 Release Notes

18 April 2017

The Utoolity team is pleased to present Tasks for AWS 2.13 – this release adds optional AWS security credentials validation at configuration time, adds explicit handling of the non standard AWS partitions AWS China and AWS GovCloud (US), adds support for the Node.js 6.10 runtime in AWS Lambda, and adds support for the Packer builder in AWS Elastic Beanstalk.

You can now ensure that provided AWS security credentials are valid, enable non standard AWS partitions as a Labs Feature, create an AWS Lambda Function with the Node.js 6.10 runtime, and create your own custom Elastic Beanstalk platform with HashiCorp's Packer.

If you are using Bamboo remote agents, please review the Tasks for AWS 2.13 Upgrade Notes for important information about this release.

Learn more and try it for free in:

Bamboo

On this page:

1 Highlights
2 Details
- 2.1 Release 2.13.1

Highlights

Validate AWS security credentials at configuration time

Any new or edited task now validates the provided AWS security credentials at configuration time by default to capture errors as early as possible.

Given long-term AWS security credentials can be disabled to allow for the highly recommended regular key rotation, it is still possible to check Skip validation to cater for this and related scenarios where the underlying AWS access key is not currently valid.

Improved support for non standard AWS partitions (experimental)

The non standard AWS regions China (Beijing) and AWS GovCloud (US) have been enabled for use already. However, due to not being based in either China or the US, we are not in a position to test this add-on with those regions directly. Thanks to feedback from users with access to those regions we have identified some resulting inconsistencies and bugs, which have been addressed by being more explicit about the underlying AWS partition concept (see the info box below for some background) – here is what you need to know about this change:

Non standard AWS partitions and their regions are now disabled by default and must explicitly be opted into as outlined in Enabling Labs Features.
- If you are Providing AWS Security Credentials via Identity Federation for AWS, the non standard partition must be enabled in both add-ons!
- If you have been using the China (Beijing) region before, you need to opt-in again as outlined in Support for the AWS China partition – existing tasks are not affected at runtime, however, the China (Beijing) region is not offered in the region widget anymore by default.
Once enabled, you need to specify the appropriate partition when Configuring an AWS Access Key so that the add-on can use the partition specific AWS endpoints at runtime.
- Since most AWS users won't have access to non standard AWS regions, the Partition option is hidden until any non standard AWS partition is enabled.

What is an AWS partition?

The AWS partition concept pretty much lacks documentation so far and is only mentioned in passing here and there, most notably within Amazon Resource Names (ARNs) and AWS Service Namespaces:

”partition – The partition that the resource is in. For standard AWS regions, the partition is aws. If you have resources in other partitions, the partition is aws-partitionname. For example, the partition for resources in the China (Beijing) region is aws-cn.”

Support for the Node.js 6.10 runtime in AWS Lambda tasks

You can now use the Node.js 6.10 runtime in the AWS Lambda Function task, see the resp. announcements:

AWS Lambda now supports Node 6.10

Node.js runtime support policy

Utoolity follows the AWS Node.js runtime support policy that has been detailed in the announcement as follows:

“You can continue to use Node v4.3 to create AWS Lambda functions. Node 0.10 was deprecated for new functions in Jan 2017, and we recommend switching to Node v4.3 or Node v6.10 at the earliest. To learn more about our Node runtime policy, visit our documentation.”

Specifically, we have deprecated the Node.js 0.10 in Tasks for AWS 2.12 and will remove the option after it can not be used anymore in AWS Lambda (April 30th 2017).

Support for i3.* EC2 instances and Packer 0.12.1 in AWS Elastic Beanstalk tasks

The available solution stacks have been updated to include the latest versions, see the resp. announcement:

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-59 – As a user, I want to validate AWS credentials so that they do not fail at runtime
Improvements
- TAWS-1099 – Update CloudFormation templates regarding upstream improvements (YAML etc.)
- TAWS-1181 – Log skipping of Step Functions execution result
- TAWS-1182 – Log execution result after stopping a Step Functions execution
- TAWS-1187 – Update available Elastic Beanstalk solution stacks (as per 2017-02-22)
- TAWS-1188 – Log connector ID when using Identity Federation for AWS credentials
- TAWS-1190 – Update available Elastic Beanstalk solution stacks (as per 2017-03-08)
- TAWS-1199 – Add support for Lambda Node.js 6.10 runtime
- TAWS-1200 – Surface support for additional Lambda region ap-south-1
- TAWS-1203 (UAA-253) – Improve ECS logging to ease task life cycle monitoring
- TAWS-1206 – Improve handling of cn-north-1
- TAWS-1207 – Add success/failure timeout handling to ECS tasks
Bugs
- TAWS-1204 – Update available Elastic Beanstalk solution stacks (as per 2017-04-05)
- TAWS-1205 (UAA-254) – Fix running of ECS tasks incorrectly failing the build
Tasks
- TAWS-966 – Drop support for Bamboo 5.8

Release 2.13.1

2017-05-09