Documentation for Identity Federation for AWS 2.4 – other releases are available in the Identity Federation 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 2 Next »

18 February 2016

Identity Federation for AWS (Bamboo)
Identity Federation for AWS (JIRA)

The Utoolity team is pleased to present Identity Federation for AWS 2.4  – this release adds an Amazon ECR Credentials Variables task to Bamboo for providing temporary Amazon EC2 Container Registry (ECR) authentication credentials to other tools by injecting them via variables into AWS unaware tasks like the Bamboo Docker task, adds a REST API for temporary Amazon EC2 Container Registry (ECR) authentication credentials, and adds support for assuming another IAM role from EC2 instance profile credentials used by an Elastic Bamboo agent.

Highlights of this release:

 

Updates for this release:

Highlights

Amazon ECR Credentials Variables task for Bamboo

Use the Amazon ECR Credentials Variables task in Bamboo to provide temporary Amazon EC2 Container Registry (ECR) authentication credentials for other tools by injecting them into AWS unaware tasks like the Bamboo Docker task.

Use Amazon ECR Credentials with Bamboo Docker task

The most frequent use case for the Amazon ECR Credentials Variables is to enable the native Bamboo Docker task to push images to an Amazon ECR repository - refer to How to push a Docker image to a repository in your Amazon ECR registry with the Bamboo Docker task for details.

Amazon ECR Credentials retrieval via REST API

Retrieve temporary Amazon EC2 Container Registry (ECR) authentication credentials via the REST API so that developers can easily integrate this feature into their own solutions.

Support for assuming another IAM Role from EC2 Instance Profile credentials

The IAM Role for EC2 (Agent) option in the AWS Credentials Variables and Amazon ECR Credentials Variables tasks for Bamboo now supports assuming another IAM role from the EC2 instance profile credentials - this enables various scenarios, notably switching to roles accross your own AWS accounts and third-party.AWS accounts (cross-account IAM roles).

Details

This release addresses the following issues:

  • Stories
    • IFAWS-504 - As a user, I want a task to create Bamboo variables from ECR credentials so that I can reuse them in scripts
    • IFAWS-505 - As a developer, I want to retrieve ECR credentials via REST so that I don't need to derive them myself
    • IFAWS-515 (UAA-74) - As a user, I want to let an instance role assume another role so that EC2 instances can be leveraged for cross-account IAM usage
  • Improvements
    • IFAWS-134 - Add sorting by header to connector table
    • IFAWS-453 - Graduate scalable group selection labs feature
    • IFAWS-477 - Redirect to main configuration screen after configuring labs features
    • IFAWS-495 - Add system usage column to connector table
    • IFAWS-496 - Add IAM read only policy to inline dialog help
    • IFAWS-509 (UAA-132) - Add conditional validation of empty IAM policy for federated users
    • IFAWS-516 - Add missing principal types to duration inline dialog help
  • Bugs
    • IFAWS-497 - Fix default button in account edit dialog not being triggered on return
    • IFAWS-498 - Mitigate missing paging functionality in connector table
    • IFAWS-507 (UAA-135) - Fix typo in generated variables popup BASH (UNIX SHELL) section
  • Tasks
    • IFAWS-467 - Drop support for Bamboo 5.1
    • IFAWS-500 - Drop support for Bamboo 5.2
    • IFAWS-501 - Drop support for Bamboo 5.3
  • No labels