Versions Compared

Old Version 40

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version Current

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Extracted 'Configuring an AWS Connector' to dedicated page.
Excerpt

Insert excerpt
_IFAWSIcon
_IFAWSIcon
nopaneltrue
Identity Federation for AWS is a foundational Amazon Web Services (AWS) integration add-on that provides Temporary AWS Security Credentials to Atlassian groups and enables access control to AWS Resources via Identity and Access Management (IAM) Policies – from a technical perspective it implements an Identity Broker/Token Vendor that uses the Atlassian Authentication System (Crowd) to Grant Access to AWS Resources. Administering the add-on comprises regular add-on maintenance as well as AWS integration and resource management.

Panel
borderColor#bbb
bgColor#eeeeee

On this page:

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

Panel
borderColor#bbb
bgColor#eeeeee

Related pages:

Administration

AWS Security Credentials Variations

Maintaining the Add-on

The following topics are applicable to regular add-on currently supports the following Principal Typesmaintenance:

Info
titleCapabilities and Restrictions

Each Principal Type has different capabilities and restrictions regarding 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)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

Configuring an AWS Connector

Create Connector

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

Image Removed

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:

    Include Page_PrincipalTypesTable_PrincipalTypesTable
  • (Optional) Add an IAM Policy (only available for principal types Federated User and Assume Role)
  • (Optional) Set the maximum number of seconds temporary credentials based on this connector can be valid - leave empty to use AWS default values

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

    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.
    1. if there are up to 100 groups, they show up immediately
    2. 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, frequently used characters like 'e' might still yield slightly sluggish behavior (depends on browser and system performance etc.), see below in case
    3. you can type more characters to filter down the search result - typing quickly should circumvent sluggishness with a very large number of groups, if any
    4. select each desired group

      • (warning) 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 another add-on like Tasks for AWS).

    • Add/Edit Account

    In order to create AWS Connectors, you need to add the 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 users for getting started with this approach.

    Note
    titleRequired IAM Permissions
    In order to use the Federated User or Assume Role principal types, you need to Grant an IAM Group Permission to Create Temporary Credentials! 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

    Configuring an AWS Connector with (optional) IAM Policy and Atlassian user group selection

    Once you have added at least one account (see above) you can configure an arbitrary number of AWS Connectors using these. A Connector requires an arbitrary name according to your needs, the account to use and an (optional) IAM Policy, see Overview of Policies. 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.

    While not required, you might want to grant one or more of your Atlassian user groups the permission to use the AWS Connector (if no group is selected, only administrators will be able to use it).

    Image Removed

    IAM Policy Examples

    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:

    Image Removed

    Filter by label (Content by label)
    showLabelsfalse
    showSpacefalse
    cqllabel = "administration" and label = "add-on" and space = currentSpace()

    Managing AWS Resources

    The following topics are applicable to AWS resource management:

    Filter by label (Content by label)
    showLabelsfalse
    showSpacefalse
    excerptTypesimple
    cqllabel = "administration" and label in ("security","credentials","aws") and space = currentSpace()

    Configuring an AWS Connector

    Refer to Configuring an AWS Connector for details.


    Configuring Advanced Scenarios

    The following topics are applicable to advanced scenarios only:

    Filter by label (Content by label)
    showLabelsfalse
    showSpacefalse
    excerptTypesimple
    cqllabel = "administration" and label = "advanced" and space = currentSpace()

    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"

    Frequently Asked Questions (FAQ)

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