Page Comparison

...

IAM user: /36hrRoot account: 15m/1hrAssumed Role an assumed role External ID and an optional IAM Policy (if absent, AWS applies a default Assumed Role AssumeRole AssumeRolearn:aws:iam::123123123123:role/UpdateAPP Delegated API Access AssumeRoleAssumeRole

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

Federated UserAssumed 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 , yet typically required IAM Policy (check Omit IAM Policy when resource-based policies are used insteadif 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! This example policy grants permission to access the AWS STS GetFederationToken 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:GetFederationTokenAssumeRole",
    "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.

15m

/12hr

/1hr

¹⁾

Temporary Credentials for Federated UsersDelegated API Access
Permissions for GetFederationTokenAssumeRole
Grant an IAM Group Permission to Create Temporary Credentials
GetFederationToken AssumeRole API action

Federated User

Yields temporary AWS security credentials for

a federated user with the Atlassian user name and an optional

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

Note
In order to use the

Federated User principal type, you need to Grant an IAM Group Permission to Create Temporary Credentials! This example policy grants permission to access the AWS STS

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:

GetFederationToken",
    "Resource": "

*"
  }]
}

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

Temporary Credentials for

GetFederationToken API action

IAM User (session token)

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

Info
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 12

New Version Current

Key