Page Comparison

Principal Type	Explanation	Credential lifetime (min/max/default)	Learn more at AWS

Federated User

Assumed Role

Yields temporary AWS security credentials for

a federated user

an assumed role with the Atlassian user name and an optional External ID and an optional IAM Policy (if absent, AWS applies a default)

Note
In order to use the

Federated User

Assumed Role principal type, you need to Grant an IAM Group Permission to Create Temporary Credentials!

The following

This example

shows a

policy

that

grants permission to access the AWS STS

GetFederationToken API - you need to add it

AssumeRole API once added to the long-term AWS security credentials you are about to use for federation (i.e. not here in this AWS Connector dialog):

Code Block

language	js
title	Example IAM Policy
collapse	true

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": "sts:

GetFederationToken

AssumeRole",
    "Resource": "

*

arn:aws:iam::123123123123:role/UpdateAPP"
  }]
}

Info
Federated User does not allow to access IAM or STS APIs, for example when creating IAM resources via CloudFormation - use or Assume Role for these scenarios instead.

Permissions for GetFederationToken

15m/12hr/1hr ¹⁾

Assume Role

`AssumeRole API action`
Federated User	Yields temporary AWS security credentials for

an assumed role

a federated user with the Atlassian user name and an optional

External ID and an optional IAM Policy (if absent, AWS applies a default

, yet typically required IAM Policy (check Omit IAM Policy when resource-based policies are used instead)

Note
In order to use the

Assume Role

Federated User principal type, you need to Grant an IAM Group Permission to Create Temporary Credentials!

The following

This example

shows a

policy

that

grants permission to access the AWS STS

AssumeRole API - you need to add it to

GetFederationToken API once added to the long-term AWS security credentials you are about to use for federation (i.e. not here in this AWS Connector dialog):

Code Block

language	js
title	Example IAM Policy
collapse	true

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": "sts:

AssumeRole

GetFederationToken",
    "Resource": "

arn:aws:iam::123123123123:role/UpdateAPP

*"
  }]
}

Info
Federated User does not allow to access IAM or STS APIs, for example when creating IAM resources via CloudFormation - use Assume Role for these scenarios instead.

IAM user: 15m/36hr/12hr

Root account: 15m/1hr/1hr

AssumeRole

Account (

IAM User (session token)

Yields temporary AWS security credentials for the selected IAM user (recommended) or AWS account (disadvised) itself

Info

Account (

IAM User (session token) does not allow to specify IAM policies or distinguish users - use Federated User or Assume Role for these scenarios instead.

IAM user: 15m/36hr/12hr

Root account: 15m/1hr/1hr

Notes ^{1) The 12hr maximum is only available with an appropriately configured Maximum Session Duration Setting for a Role.}

Versions Compared

Old Version 8

New Version Current

Key