Documentation for Tasks for AWS 2.10 – other releases are available in the Tasks for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Current »

15 August 2014

The Utoolity team is pleased to present Tasks for AWS 2.4 – this release adds shared AWS security credentials management by integrating with Identity Federation for AWS (Bamboo), persists credentials of type Inline through the Bamboo EncryptionService API, and adds support for Windows Server 2012 R2 and Server Core solution stacks in AWS Elastic Beanstalk environments.

Highlights of this release:

Updates for this release:

Highlights

Shared AWS security credentials management

You can now manage AWS security credentials centrally by means of an integration with the Identity Federation for AWS (Bamboo) add-on:

  • add long-term AWS security credentials (IAM users) once, configure AWS access for Atlassian groups with temporary credentials and fine grained permissions via IAM Policies thereafter (Identity Broker)
  • grant easy access to AWS resources directly via menu links to the AWS Management Console (see the User's Guide for details)
    • (lightbulb) this can optionally include access to your elastic agents for administrators (or any other group with access to the resp. AWS Connector)

No Charge

Usage of Identity Federation for AWS (Bamboo) is free for Tasks for AWS licensees, see the Licensing & Purchasing FAQ for details.

Improved security of Inline credentials persistence

AWS security credentials of type Inline are now persisted through the Bamboo EncryptionService API on Save for new or existing tasks.

No Real Encryption

Please note that the Bamboo EncryptionService API naming is misleading for the time being - as properly phrased in the method summary of com.atlassian.bamboo.security.EncryptionServiceImpl, the decrypt()/encrypt() methods just provide means to obfuscate sensitive data.

No Automatic Migration

Existing task configurations are not upgraded automatically, you need to explicitly edit and save them once. Given most users want to upgrade to shared AWS credentials managed via Identity Federation for AWS instead, we felt this to be an acceptable compromise - please get in touch if your situation requires a different approach, we are willing to discuss this on a case by case base.

Support for Windows Server 2012 R2 and Server Core solution stacks in AWS Elastic Beanstalk tasks

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. announcement and related posts:

Details

This release addresses the following issues:

  • Stories
    • TAWS-39 (UAA-5) - As a user, I want to manage AWS credentials centrally so that I do not need to enter them for every task
  • Improvements
    • TAWS-281 (UAA-5) - Adjust task credentials storage to facilitate Bamboo EncryptionService API
    • TAWS-366 - Update available Elastic Beanstalk solution stacks (as per 20140806)
  • Bugs
    • TAWS-283 - Fix unhelpful error message 'Encountered internal plugin error'
    • TAWS-298 - Verify add-on working after disable/enable cycle (own as well as IFAWS)
    • TAWS-335 - Fix regressions on task execution on remote agents

Updates

Release 2.4.8

This release addresses the following issues:

  • Improvements

    • TAWS-304 - Add optional ANT regexp based renaming to S3 upload action

    • TAWS-450 - Expand source bundle fieldgroup on Elastic Beanstalk Application Version create action by default

    • TAWS-451 - Add configurable verification period to Elastic Beanstalk Environment await green health logic
    • TAWS-452 - Update available Elastic Beanstalk solution stacks (as per 20141008)

Release 2.4.7

This release addresses the following issues:

  • Improvements

    • TAWS-399 (UAA-23) - Add Elastic Beanstalk Environment create option to await green health status

    • TAWS-400 (UAA-24) - Add CNAME based environment selection

  • Bugs
    • TAWS-417 - Fix default button in task configuration screens

    • TAWS-418 (UAA-17) - Fix incorrect version tag yielding Elastic Beanstalk sample app instead

    • TAWS-441 - Fix Bamboo variable creation prefix for Elastic Beanstalk Application Version task

Release 2.4.6

This release addresses the following issues:

  • Bugs
    • TAWS-430 - Fix CloudFormation stack update action not creating expected output variables

Release 2.4.5

This release addresses the following issues:

  • Improvements
    • TAWS-45 - Add EC2 resource filter handling
  • Bugs
    • TAWS-389 - Fix lack of explanation/link below AWS Credentials Source widget

Release 2.4.4

This release addresses the following issues:

  • Improvements
    • TAWS-64 (UAA-27) - Add CloudFormation Stack create option to delete the stack on failure
  • Bugs
    • TAWS-416 - Fix Bamboo variable substitution for encrypted 'Inline' credentials
  • Technical Debt
    • TAWS-396 - Constrain ServiceProxyDestroyedException workaround to Bamboo <= 5.6.0 (see BAM-14801 for details)

Release 2.4.3

This release addresses the following issues:

  • Bugs
    • TAWS-398 (UAA-29) - Fix exception on Identity Federation for AWS credentials usage in automatically triggered deployment projects

Release 2.4.2

This release addresses the following issues:

  • Improvements
    • TAWS-362 (UAA-25) - Add CloudFormation Stack update action override to pass task if no updates are to be performed

Release 2.4.1

This release addresses the following issues:

  • Improvements
    • TAWS-371 - Update available Elastic Beanstalk solution stacks (as per 20140814)
  • Bugs
    • TAWS-369 - Fix typo in template examples inline dialog
    • TAWS-372 - Fix 404 due to link targeting old IFAWS plugin key
  • No labels