Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to release 2.12.0.


Excerpt

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


Panel
borderColor#bbb
bgColor#eeeeee

On this page:

Table of Contents
maxLevel2
exclude(Popular.*|Recent.*)


Panel
borderColor#bbb
bgColor#eeeeee

Related pages:


Configuration

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:

CredentialsSelect 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:

Info
titleCapabilities 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.

Include Page
_PrincipalTypesTable
_PrincipalTypesTable

Policy ARNs(Conditional) Specify a Managed IAM Policy ARN (supported for principal types Assume Role and Federated User)
  • (lightbulb) 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.
Policy(Conditional) Specify an Inline IAM Policy (supported for principal types Federated User and Assume Roletypes Assume Role and Federated User)
  • (lightbulb) 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:

Info

Administrators always have permission to use all Connectors.

  1. click into the selection box to search for groups
  2. start typing to narrow down the selection

    Info
    titlePerformance 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.

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

    • (warning) 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 (Content by label)
max8
showSpacefalse
sorttitle
excerptTypesimple
cqllabel = "administration" and label in ( "kb-how-to-article" , "kb-troubleshooting-article" ) and label = "identity-federation-for-aws" and label = "connector"

Frequently Asked Questions (FAQ)

Include Page
UAA:_FAQHeaderQuestionsForConfluence
UAA:_FAQHeaderQuestionsForConfluence

Questionslist macro
filterpopular
asktrue
limit8
topicidentity-federation-for-aws,connector