Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Restructured/Shortened configuration instructions.
Excerpt

In order to enable access to your AWS resources, you need to create at least one AWS Connector. You can access this functionality via the AWS Connectors configuration screen.

Panel
borderColor#bbb
bgColor#eeeeee

On this page:

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

Panel
borderColor#bbb
bgColor#eeeeee

Related pages:

AWS Security Credentials Variations

The add-on currently supports the following 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.


Principal TypeAWS DocumentationAPI actionCredential lifetime (min/max/default)Notes
(tick)Federated UserTemporary Security Credentials to Enable Access for Federated UsersGetFederationToken

IAM user: 15m/36hr/12hr

Root account: 15m/1hr/1hr


(tick)Assume RoleTemporary Security Credentials for Delegating API AccessAssumeRole15m/1hr/1hr


(tick)IAM UserTemporary Security Credentials to Enable Access for IAM UsersGetSessionToken

IAM user: 15m/36hr/12hr

Root account: 15m/1hr/1hr

(tick)IAM RoleTemporary Security Credentials for Delegating API AccessAssumeRole15m/1hr/1hr
(error)SAML FederationTemporary Security Credentials for SAML FederationAssumeRoleWithSAML15m/1hr/1hrSupport for SAML is not on our roadmap, see the resp. FAQ for details

Create/Edit Connector

Clicking Create Connector (or Edit later on) opens the Edit AWS Connector dialog:

Image Removed

Here are the required steps:

  • Select the account to use (you might need to add accounts first)
  • Choose this Connector's name
  • Choose the Principal Type - there are the following choices currently

    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.

    Image Added


    Complete the following settings:

    Account (IAM User) Select the long-term AWS security credentials to derive temporary AWS security credentials from - see also add/edit accounts below.
    Connector Name

    Specify a custom name to identify this connector.

    Principal Type

    Select one of the supported principal types:

    Include Page
    _PrincipalTypesTable
    _PrincipalTypesTable

    IAM Policy(
    Optional
    Conditional)
    Add
    Specify an IAM Policy (
    only available You can reuse existing policies already in use in your organization or create new policies tailored to your use case via the AWS Policy Generator and test them with the IAM Policy Simulator.
    supported for principal types Federated User and Assume Role)
    • (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.
    Maximum Duration

    (Optional) Set the maximum number of seconds temporary credentials based on this connector can be valid - leave empty to use AWS default values

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

    Image Added

    Info

    Administrators always have permission to use all Connectors.

    Image Removed

    1. click into the selection box to search for groups
      • (info) Bamboo < 5.6 and JIRA < 6.2 feature a different user interface for group selection still, see 
        Jira Legacy
        serverJIRA (utoolity.atlassian.net)
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdfac61c2e-db0a-39da-bb3c-e0dc0ef556f0
        keyUAA-89
         for details.
  • if there are up to 100 groups, they show up immediately
  • if
    1. 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
    1.  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

    (depends on browser and system performance etc.), see below in caseyou can type more characters to filter down the search result
    1. - typing quickly should circumvent such sluggishness

    with a very large number of groups
    1. , if any!

    2. 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
    another
    other add-
    on




    Add/Edit Account

    In order to create AWS Connectors, you need to add at least one account resp. IAM User, which provides the required long-term AWS security credentials used to derive temporary AWS security credentials for your Atlassian users, see Create individual IAM users for getting started with this approach.

    Noteinfo
    titleRequired IAM Permissions
    In order to use the The Federated User or and Assume Role principal types , you need to Grant an IAM Group Permission require Permissions to Create Temporary Credentials! See - see the Principal Types table above for details.

    Accounts are added/edited/deleted inline while creating/editing an AWS Connector. All fields are required, you can select an arbitrary name according to your needs.

    Info
    Editing an existing account will change it for all AWS Connectors using it.

    Clicking Create Account (or Edit later on) opens the Edit Account (IAM User) dialog:

    Image Removed

    To configure an Account (IAM User):

    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.
    3. Click Edit for an existing Account (IAM User), or click Add Account to create a new one.

    Image Added

    Complete the following settings:

    Account NameSpecify a custom name to identify this account.
    Access Key ID

    Provide the Access Key ID of your long-term AWS Security Credentials.

    Secret Access Key
    Provide the Secret Access Key of your long term AWS Security Credentials.


    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)

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