Configuring an AWS Connector

In order to enable access to your AWS resources, you need to create at least one AWS Connector.


To configure an AWS Connector:

  1. Navigate to the Identity Federation for AWS configuration.

  2. Click Edit for an existing AWS Connector, or click Create connector to create a new one.

Complete the following settings:


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

IAM role for EC2/ECS

 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 enable the IAM role for EC2/ECS credentials provider to 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. The resulting pseudo access key [IAM role for EC2/ECS] is added to the end of the credentials widget and can be either used directly via 'Provided' or assume another role via the ' Assumed Role' principal types.

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.

Policy ARNs

(Conditional) Specify a Managed IAM Policy ARN (supported for principal types Assume Role and Federated User)

 Clicking on 'Policy ARN 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  IAM Policy Simulator are also provided.


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

 Clicking on '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.


(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).


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

By default, administrators always have permission to use all connectors – this can be adjusted by Disabling implicit connector visibility for administrators (experimental).

  1. click into the selection box to search for groups

  2. 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!

  3. select each desired group
     all changes persist on save of the connector only


(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®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.