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

Policy (if absent, AWS applies a default)

Note
In order to use the

Federated User Principal Type

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

Info

A few services aren't currently supported by Federated User - use Account (IAM User) for these instead:

AWS CloudFormation
Amazon Elastic MapReduce
AWS Elastic Beanstalk

Permissions in Temporary Security Credentials for Federated Users

This example policy grants permission to access the AWS STS 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:AssumeRole",
    "Resource": "arn:aws:iam::123123123123:role/UpdateAPP"
  }]
}

15m/12hr/1hr ¹⁾

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

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

features

scenarios instead.

Permissions in Temporary Security

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 3

New Version Current

Key