Versions Compared

Old Version 6

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

Saved on

compared with

New Version 7

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

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added table for Principal Type.
Section
Column
width64%

Identity Federation for AWS is mainly a system integration and API add-on that provides Temporary 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.

Info
titleTemporary Security Credential Variations
At the moment the add-on supports Temporary Security Credentials to Enable Access for Federated Users, support for Temporary Security Credentials for Delegating API Access might be added later on.
Column
width32%
Panel
bgColor#eeeeee

On this page:

Table of Contents

...

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 Connector management screen.

Create/Edit Connector

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

...

  1. Select the account to use (you might need to add accounts first)
  2. Choose this Connector's name

  3. Choose the Principal Type - there are tow choices currently

    Principal TypeExplanationLearn more at AWS
    Federated User

    Yields temporary credentials for a federated user with the Atlassian user name and an optional IAM policy (if absent, AWS applies a default)

    Info

    A few services aren't currently supported by Federated User - use Account (IAM User) for these instead:

    AWS CloudFormation
    Amazon Elastic MapReduce
    AWS Elastic Beanstalk

    		Permissions in Temporary Security Credentials for Federated Users
    Account (IAM User)

    Yields temporary credentials for the selected IAM user (recommended) or AWS account (disadvised) itself

    Info
    Account (IAM User) does not allow to specify IAM policies or distinguish users - use Federated User for these features instead.
    		Permissions in Temporary Security Credentials for IAM Users
  4. (Optional) Add an IAM Policy (only available for Principal Type Federated User

  5. (Optional) Grant the permission to use this Connector to one or more of your JRIA groups

    Info
    Administrators always have the permission to use all Connectors

...

Configuring an AWS Connector with (optional) IAM Policy and JIRA 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).

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) - a link to the AWS Policy Generator is also provided: