The Utoolity team is pleased to present Identity Federation for AWS 2.0 – this major release adds support for Atlassian Bamboo, adds system scoped AWS credentials for elevated API usage without an active user session, and upgrades the API to version v2 to support secure configuration migration across instances/installations.
Support for Atlassian Bamboo
Use Identity Federation for AWS in Atlassian Bamboo to gain the following benefits:
easy access to elastic agents via the AWS Management Console (see the Using Identity Federation for AWS for details)
reuse by other add-ons, such as Tasks for AWS
Cross Product Support
Identity Federation for AWS aims to be a cross product solution and currently supports JIRA, Confluence, and Bamboo (see the Identity Federation for AWS Compatibility Notes for details) - please don't hesitate to get in touch, if you are interested in support for other Atlassian products, we are eager to learn more about your use case and adjusting our respective roadmap accordingly.
Dedicated Add-ons per Application
Bamboo and JIRA are each supported via a new dedicated add-on per Atlassian application due to Marketplace restrictions for cross-product add-ons:
the former JIRA only add-on will be archived, but can technically be used in parallel to ease migrating to the new version (minor usability issues apply)
the add-ons operate independent right now, i.e. credentials need to be managed separately for each and duplicated if desired - cross-product usage via application links is on our mid-term roadmap
System scoped AWS credentials
An AWS connector can now be denoted as System scoped and then used from elevated code (e.g. within another add-on) without an active user session to allow usage within Atlassian Bamboo's Tasks for example, as facilitated by Tasks for AWS.
REST API v2
The API has been upgraded to Globally Unique Identifier (GUID) based IDs to support secure configuration migration across instances and installations (refer to the Developer Guide for details).
For more details about this release, please refer to the Identity Federation for AWS 2.0 Release Notes.