31 May 2013

The Utoolity team is pleased to present Identity Federation for AWS 1.1 – this release adds a second principal type Account (IAM User) to expand the available integration scenarios, significantly improves the Atlassian Design Guidelines (ADG) compliance and adds sample IAM Policies to ease getting started.

On this page:

Highlights

Second Principal Type Account (IAM User)

Use temporary credentials for a configured IAM user or AWS account itself to enable both simplified integration scenarios as well as previously unavailable services (AWS CloudFormation, Amazon Elastic MapReduce, AWS Elastic Beanstalk).

Improved Atlassian Design Guidelines compliance

The initial user interface has been revised to significantly improve the Atlassian Design Guidelines (ADG) compliance.



Sample IAM Policies

The configuration dialog now offers a few example Identity and Access Management (IAM) Policies to ease getting started.

Details

This release addresses the following issues:

  • Stories

    • IFAWS-151 - As an administrator, I want to facilitate the GetSessionToken API so that I can use services not available otherwise

  • Improvements

    • IFAWS-63 - Add useful default policy and/or example policies

    • IFAWS-19 - Review/Adjust UI for compliance with the Atlassian Design Guidelines (ADG)

  • Bugs

    • IFAWS-140 - Ensure correct field focus for Account edit popup

    • IFAWS-133 - Adjust field width in 'Add new AWS Account' dialog

Updates

Release 1.1.1

This release addresses the following issues:

  • Bugs

    • IFAWS-167 - Fix issue collector link causing a horizontal scrollbar

  • Technical Debt

    • IFAWS-168 - Review/Adjust API for compliance with the Atlassian REST API Design Guidelines