Configuring an AWS Connector

Configuration

To configure an AWS Connector:

Navigate to the Identity Federation for AWS configuration.
Click Edit for an existing AWS Connector, or click Create connector to create a new one.

Complete the following settings:

Credentials Select the long-term AWS security credentials to derive temporary AWS security credentials from - refer to Configuring an AWS Access Key for details.

Connector Name

Specify a custom name to identify this connector.

Principal Type

Select one of the supported principal types:

Capabilities and Restrictions

Each principal type has different capabilities and restrictions regarding credential lifetime, single sign-on (SSO) to the AWS Management Console, Multi-Factor Authentication (MFA) and calling the IAM and STS APIs in turn, see Comparing Features of AWS STS APIs for details.

Principal Type	Explanation	Credential lifetime (min/max/default)	Learn more at AWS
Assumed Role	Yields temporary AWS security credentials for an assumed role with the Atlassian user name and an optional External ID and an optional IAM Policy (if absent, AWS applies a default) In order to use the 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 `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): Example IAM Policy Expand source { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": "sts:AssumeRole", "Resource": "arn:aws:iam::123123123123:role/UpdateAPP" }] }	15m/12hr/1hr ¹⁾	Temporary Credentials for Delegated API Access Permissions for AssumeRole Grant an IAM Group Permission to Create Temporary Credentials `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) 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): Example IAM Policy Expand source { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": "sts:GetFederationToken", "Resource": "" }] } 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 Federated Users Permissions for GetFederationToken Grant an IAM Group Permission to Create Temporary Credentials `GetFederationToken API action`
IAM User (session token)	Yields temporary AWS security credentials for the selected IAM user (recommended) or AWS account (disadvised) itself 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	Temporary Credentials for IAM Users Permissions for GetSessionToken `GetSessionToken API action`
Notes	^{1) The 12hr maximum is only available with an appropriately configured Maximum Session Duration Setting for a Role.}

IAM Policy

(Conditional) Specify an IAM Policy (supported for principal types Federated User and Assume Role)

Clicking on 'IAM Policy Examples' allows you to select from a few example policies to ease getting started (just click one to copy it to the policy field) - links to the AWS Policy Generator and the IAM Policy Simulator are also provided.

Duration

(Optional) Set the number of seconds temporary credentials based on this connector are valid - leave empty to use the AWS default credential lifetime (refer to table Principal Types above for details).

Groups

(Optional) Grant the permission to use this Connector to one or more of your Jira or Bamboo groups:

Administrators always have permission to use all Connectors.

click into the selection box to search for groups
start typing to narrow down the selection
Performance with more than 100 groups

If there are more than 100 groups, you need to type at least one character to make all matching groups appear.
Depending on the number of groups and naming scheme paired with browser and system performance, frequently used characters like 'e' might still yield slightly sluggish behavior - typing quickly should circumvent such sluggishness, if any!
select each desired group
- all changes persist on save of the connector only

Scope (Optional) Select System Scope to allow usage of this AWS Connector from elevated code without an active user session (e.g. by other apps like Tasks for AWS and Automation with AWS).

How-to Articles

Filter by label

There are no items with the selected labels at this time.

Frequently Asked Questions (FAQ)

Atlassian account required

Due to a regression within Questions for Confluence Cloud, you need to log in with your Atlassian ID (or sign up for a new account) to access these automatically curated FAQs (refer to UAA-312 for the background).