15 August 2014
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)
- this can optionally include access to your elastic agents for administrators (or any other group with access to the resp. AWS Connector)
No Charge
Improved security of Inline credentials persistence
AWS security credentials of type Inline are now persisted through the
No Real Encryption
Support for Windows Server 2012 R2 and Server Core solution stacks in the 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-366 - Update available Elastic Beanstalk solution stacks 20140806
- TAWS-281 (UAA-5) - Adjust task credentials storage to facilitate Bamboo EncryptionService API
- Bugs
- TAWS-335 - Fix regressions on task execution on remote agents
- TAWS-298 - Verify add-on working after disable/enable cycle (own as well as IFAWS)
- TAWS-283 - Fix unhelpful error message 'Encountered internal plugin error'