Page Comparison

AWS Security Credentials Variations

The add-on currently supports the

following Principal Types:

	Principal Type	AWS Documentation	API action	Credential lifetime (min/max/default)	Notes
	Federated User	Temporary Security Credentials to Enable Access for Federated Users	GetFederationToken	IAM user: 15m/36hr/12hr Root account: 15m/1hr/1hr
	IAM User	Temporary Security Credentials to Enable Access for IAM Users	GetSessionToken	IAM user: 15m/36hr/12hr Root account: 15m/1hr/1hr
	IAM Role	Temporary Security Credentials for Delegating API Access	AssumeRole	15m/1hr/1hr
	SAML Federation	Temporary Security Credentials for SAML Federation	AssumeRoleWithSAML	15m/1hr/1hr	Support for SAML is not on our roadmap, see the resp. FAQ for details

AWS Connector Management

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 Modified

Create/Edit Connector

Clicking Create Connector (

or Edit

 later on) opens

the Edit AWS Connector

 dialog:

Image Modified

Here are the required steps:

1. Select the account to use (you might need

1. to add accounts

1.  first)
2. Choose this Connector's name

3. Choose

1. the Principal Type - there are the following choices currently:

   Include Page
   _PrincipalTypesTable _PrincipalTypesTable

   
   

2. (Optional) Add

1. an IAM Policy (only available for principal

1. types Federated

1. User and

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

3. (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 Modified

   
   
   1. click into the selection box to search for groups
   • • 

1. • •  Bamboo < 5.6 and JIRA < 6.2 feature a different user interface for group selection still,

1. • • see 

       Jira Legacy
       server JIRA (utoolity.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId fac61c2e-db0a-39da-bb3c-e0dc0ef556f0 key UAA-89

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

1. 1. •  depending on the number of groups and naming scheme, frequently used characters like 'e' might

1. 1. •  still yield slightly sluggish behavior (depends on browser and system performance etc.), see below in case
   2. 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
   3. select each desired group

   • • 

1. • •  all changes persist on save of the connector only

2. (Optional)

1. Select System Scope

1.  to allow usage of this AWS Connector from elevated code without an active user session (e.g. by another add-on

1. 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.

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.

Clicking Create

Account (

or Edit

 later on) opens

the Edit Account (IAM User) dialog:

Image Modified

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 Modified

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 Modified

Advanced Topics

The following topics are applicable to advanced scenarios only:

• Configuring the AWS Client

• Configuring an Outbound HTTP(S) Proxy

• Enabling Labs Features