Versions Compared

Old Version 1

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version 2

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed release date.

10 October November 2014

Excerpt
Tip
iconfalse
Div
stylepadding: 0 0.5em 0.5em 0.5em
Div
stylefloat: right; margin: 0 0 0.5em 0.5em

Tasks for AWS

 

Div
stylemargin: 0 1em 1em 0

The Utoolity team is pleased to present Tasks for AWS 2.5 – this release adds support for IAM Roles (both for Amazon EC2 and the AssumeRole API), adds reuse of existing template and change of SNS topic on CloudFormation updates, and improves CloudFormation template parameter management by converting to JSON format.

Highlights of this release:

Table of Contents
minLevel3
excludeRelease [1-9]\.[0-9]\.[1-9]+

Updates for this release:

Table of Contents
minLevel3
includeRelease [1-9]\.[0-9]\.[1-9]+

Highlights

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1

Support for IAM Roles

There are now two variations for working with IAM Roles:

IAM Roles for Amazon EC2

You can now use IAM Roles for Amazon EC2 to skip credentials configuration all together.

Note
titleElastic Bamboo only supports this as of Bamboo 5.6

This feature requires the Amazon EC2 instance running the agent to be started with an EC2 instance profile. This could be the host of the Bamboo server itself for local agents or regular remote agents that happen to run on an EC2 instance. However, Elastic Bamboo only supports configuring elastic images with an instance profile as of Bamboo 5.6.

IAM Roles for AssumeRole API

The embedded Identity Federation for AWS 2.1 release adds a new principal type 'Assume Role' to support IAM roles for delegating API access to AWS resources in other accounts (cross-account usage) and enabling API access to the IAM service itself.

Panel
borderColor#F3F3F3
bgColor#FFFFFF

Reuse of existing template and change of SNS topic for CloudFormation updates

Two recent CloudFormation API additions are now available during stack updates too:

  • AWS CloudFormation now provides you an option to update a stack by passing in only parameters. In this option, CloudFormation automatically uses the stack template it already has.
  • AWS CloudFormation has also introduced the ability to add or remove the Amazon SNS topics you use to monitor stack creation and updates.
Panel
borderColor#F3F3F3
bgColor#FAFAFA

Conversion of CloudFormation template parameter management to JSON

The former CSV format has severe usability issues for anything but a trivial amount of template parameters and does not support using existing values on updates. To address these deficits and foster reuse of configuration between the various AWS tools, the parameter management has been aligned to the JSON format supported by the AWS CLI.

  • (info) The legacy CSV format remains available in tasks configured in previous versions for backwards compatibility, newly configured tasks support the new JSON format only.
  • (info) An opt-in conversion is offered when the legacy CSV parameter composition can be translated into JSON automatically.
Panel
borderColor#F3F3F3
bgColor#FFFFFF

Support for Java 8 Tomcat 8, Python 3.4, Java 7 GlassFish 4.0, and Java 8 GlassFish 4.1

The available solution stacks have been updated to include the latest versions, notably including the recently introduced Windows Server 2012 R2 and Server Core stacks, see the resp. announcements:

(info) The latter three platforms are based on the new category of supported platforms – Preconfigured Docker:

[...] This category of platforms is based on the language stacks provided by the Docker Official Repos on the Docker Hub Registry and allows us to provide you with the bleeding edge versions of additional language/framework platforms sooner. [...]

The ‘Preconfigured Docker’ platforms are delivered as Docker containers, this allows you to develop and test your applications locally using the same container that your application will be deployed to on Elastic Beanstalk. To run the Docker container locally, simply add a Dockerfile in your application’s root folder with the appropriate 'FROM' line, based on the platform you are using

Details

This release addresses the following issues:

  • Stories
    • TAWS-50 (UAA-26) - As a user, I want to reuse AWS credentials provided by an IAM role for EC2 so that I do not need to enter them for every task
  • Improvements
    • TAWS-57 - Improve CloudFormation template parameter management
    • TAWS-284 - Support reuse of existing template on CloudFormation update actions
    • TAWS-285 - Support change of SNS topic on CloudFormation update actions
    • TAWS-336 - Support CloudFormation stack ids
    • TAWS-462 (UAA-46) - Convert CloudFormation parameter input to JSON
    • TAWS-465 - Verify/Add support for eu-central-1 (Frankfurt) region
    • TAWS-472 - Update available Elastic Beanstalk solution stacks (as per 20141031)
    • TAWS-473 - Update available Elastic Beanstalk solution stacks (as per 20141105-1 / 20141105-2)
  • Bugs
    • TAWS-466 (UAA-48) - Fix official S3 ACL header format not being supported