Tasks for AWS 2.14 Release Notes

11 May 2017

The Utoolity team is pleased to present Tasks for AWS 2.14 – this release adds support for providing task configuration as code via URLs, adds support for sharing S3 objects via pre-signed URLs in Amazon S3, adds support for Custom Platforms in AWS Elastic Beanstalk, and adds support for the Python 3.6 runtime in AWS Lambda.

You can now inject task configuration for JSON and YAML parameters via URLs to provide configuration as code, generate a pre-signed S3 URL to temporarily share private S3 objects with subsequent build steps, use your own custom Elastic Beanstalk platform created with HashiCorp's Packer, and create an AWS Lambda Function with the Python 3.6 runtime.

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

Learn more and try it for free in:

Bamboo

On this page:

1 Highlights
2 Resolved issues
- 2.1 Release 2.14.7
- 2.2 Release 2.14.6
- 2.3 Release 2.14.5
- 2.4 Release 2.14.4
- 2.5 Release 2.14.3
- 2.6 Release 2.14.2
- 2.7 Release 2.14.1
- 2.8 Release 2.14.0

Highlights

Provide task configuration as code

Just in time with Atlassian's introduction of Bamboo Specs in Bamboo 6.0, we are contributing our own improvement to configuration as code by offering to Inject task configuration via URLs:

As of Tasks for AWS 2.14, you can provide JSON or YAML based task parameters as code by referencing configuration files via URLs. You can reference a configuration file from the build working directory via the file:// protocol, or from a publicly accessible web location via the http:// and https:// protocols (this also allows to reference a configuration file from a private S3 bucket via a pre-signed URL).

Configuration as code

One of the most important aspects of applied DevOps within a CI/CD software delivery pipeline is to maintain infrastructure and configuration as code. You can mix and match the available options to provide task configuration as code to successively migrate your current build configurations to a fully managed and versionized build setup.

Use custom platforms in Elastic Beanstalk environments

You can now use Custom Platforms as a third configuration source in the AWS Elastic Beanstalk Environment task:

AWS Elastic Beanstalk is excited to announce the support for Custom Platforms. You can now create and manage your own custom Elastic Beanstalk platforms as per your application and configuration requirements. Earlier, you could only use the pre-configured platforms provided by AWS Elastic Beanstalk. With pre-configured platforms, to customize your environment configuration you have to add .ebextensions to your application sources bundle or use the limited configuration options available on the Management Console or EB CLI. With Custom Platform, as an author you get greater control over the AMI, metadata, and configuration options. This feature allows you to enforce and manage standardization and your best practices across your Elastic Beanstalk environments. For example, you can now create your own platforms on Ubuntu or Red Hat Enterprise and customize your instances with languages/frameworks currently not supported by Elastic Beanstalk e.g. Rust, Sinatra etc.

Custom platforms are region specific and need to be deliberately created, refer to Custom Platforms for details.

Use the Python 3.6 runtime in AWS Lambda functions

You can now use the Python 3.6 runtime in the AWS Lambda Function task, see the resp. announcement:

AWS Lambda Supports Python 3.6