Configuration
To configure an AWS Connector:
AWS Security Credentials Variations
The add-on currently supports the following Principal Types- Navigate to the Identity Federation for AWS configuration.
- Click Edit for an existing AWS Connector, or click Create connector to create a new one.
Complete the following settings:
Credentials | Select 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:
|
|
Choose the Principal Type - there are the following choices currently:
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 |
Create/Edit Connector
Clicking Create Connector (or Edit later on) opens the Edit AWS Connector dialog:
Here are the required steps:
| ||||||
IAM Policy | ( |
Conditional) |
Specify an IAM Policy ( |
supported for principal types Federated User and Assume Role) |
| |
Maximum Duration | (Optional) Set the maximum number of seconds temporary credentials based on this connector can be 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:
|
|
|
|
|
| |
Scope | (Optional) Select System Scope to allow usage of this AWS Connector from elevated code without an active user session (e.g. by |
other add- |
ons like Tasks for AWS |
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.
Note | ||
---|---|---|
| ||
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:
and Automation with AWS). |
How-to Articles
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Frequently Asked Questions (FAQ)
Questionslist macro | ||||||||
---|---|---|---|---|---|---|---|---|
|