Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed Bamboo variable namespace and scope concept markup.


Div
stylepadding: 0 0.5em 0.5em 0.5em


Excerpt


Div
stylemargin: 0 1em 0.8em 0

20 Oct 2020

The Utoolity team is pleased to present Identity Federation for AWS 2.14this release adds an IAM role for EC2/ECS credentials provider and introduces namespace and scope handling for generated Bamboo variables.

You can now provide AWS security credentials via an IAM role for EC2/ECS when you run your Atlassian products on Amazon EC2, Amazon ECS, or AWS Fargate, and you can adjust the namespace and scope of generated Bamboo variables.





Panel
borderColor#bbb
bgColor#fff


Div
stylefloat: left; margin: 0

Learn more and try it for free in:


BambooBitbucket | Confluence | Jira



Panel
borderColor#bbb
bgColor#eeeeee

On this page:

Table of Contents
maxLevel3
exclude(Popular|Recent).*


Highlights (Core)

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1

Provide AWS security credentials via an IAM role for EC2/ECS


asdfasdfasdf

Image Modified

You can now enable the IAM role for EC2/ECS credentials provider via a feature flag. If you have provisioned your Atlassian workloads on Amazon EC2 (for example, via the Atlassian Data Center on AWS Quick Starts), Amazon ECS, or AWS Fargate, you can now benefit from the convenience and flexibility of providing AWS security credentials via IAM roles for Amazon EC2 instances and IAM roles for Amazon ECS tasks.

Note
titleSecurity assessment

The convenience of IAM roles for Amazon EC2 instances have the downside of a less explicit security posture and more indirect regression potential, as further outlined in

Jira
serverSystem JIRA
serverIdfac61c2e-db0a-39da-bb3c-e0dc0ef556f0
keyUAA-49
. The feature currently requires an opt-in via a feature flag accordingly, and we also recommend the principal type 'Assume Role' rather than 'Provided' to gain the actual permissions via another role instead of the one directly attached to the EC2 instance. Either way, please make sure you have thoroughly assessed the security configuration of your underlying EC2 instance(s) and the attached or assumed IAM roles.


Info
titleFeature flag status

Status
subtletrue
colourYellow
titleLabs feature

We are committed to fully support this feature going forward, which is the first exploratory step in our journey to offer more choices and flexibility in providing AWS security credentials via a dedicated SPI. However, due to requiring architectural changes, we are releasing an opt-in early version as a labs feature so that we can provide it sooner and gather feedback around usability and security questions before bringing it front and center to all customers. Please provide feedback via the built-in Jira integration, or contact us directly.


Highlights (Bamboo)

Panel
borderColor#F3F3F3
bgColor#FFFFFF

Adjust generated Bamboo variable namespace and scope

Similar to the Inject Bamboo variables task that has been included with Bamboo as of release 6.7, you can now specify the namespace and scope for Bamboo variables generated by the AWS Credentials Variables and Amazon ECR Credentials Variables tasks to enable more flexible build orchestration. You can now pass a variable between stages, pass a variable from a plan to a deployment project, and you can use multiple tasks within the same job without overriding variables from preceding tasks by adjusting the namespace. The tasks default to the preceding behavior with local scope and a custom.aws namespace so that this remains an opt-in choice for advanced use cases.


Resolved issues

Release 2.14.0

2020-10-20

This release addresses the following issues:

Core

  • Stories
    • IFAWS-301 (UAA-49) – As an administrator, I want to provide AWS credentials via an IAM role for EC2 so that I do not need to add an access key
  • Improvements
    • IFAWS-1339 – Add app configuration link tooltip
  • Bugs
    • IFAWS-1359 – Fix missing 40x when using PUT with additional JSON fields
    • IFAWS-1376 (UAA-435) – Fix GET not returning the JSON field when connector scope has not been configured
    • IFAWS-1438 (UAA-462) – Fix insufficient credentials validation of access key dialog

Bamboo

  • Stories
    • IFAWS-1423 – As a user, I want to be in control of variable namespace and scope so that I gain simplified plan composition
  •  Tasks
    • IFAWS-1350 – Drop support for Bamboo 6.5
    • IFAWS-1403 – Drop support for Bamboo 6.6

Bitbucket

  • Tasks
    • IFAWS-1348 – Drop support for Bitbucket 5.9
    • IFAWS-1351 – Drop support for Bitbucket 5.10
    • IFAWS-1353 – Drop support for Bitbucket 5.11
    • IFAWS-1405 – Drop support for Bitbucket 5.12
    • IFAWS-1407 – Drop support for Bitbucket 5.13
    • IFAWS-1410 – Drop support for Bitbucket 5.14

Confluence

  • Tasks
    • IFAWS-1347 – Drop support for Confluence 6.8
    • IFAWS-1352 – Drop support for Confluence 6.9
    • IFAWS-1404 – Drop support for Confluence 6.10
    • IFAWS-1408 – Drop support for Confluence 6.11

Jira

  •  Tasks
    • IFAWS-1349 – Drop support for Jira 7.9
    • IFAWS-1354 – Drop support for Jira 710
    • IFAWS-1406 – Drop support for Jira 7.11
    • IFAWS-1409 – Drop support for Jira 7.12