...
...
| title | Temporary AWS Security Credentials Variations |
|---|
...
...
- Temporary Security Credentials to Enable Access for Federated Users
- Temporary Security Credentials to Enable Access for IAM Users
Support for Temporary Security Credentials for Delegating API Access will be added later on.
...
| width | 32% |
|---|
...
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 Connector management screen.
Create/Edit Connector
Clicking Create Connector (or Edit later on) opens the Edit AWS Connector dialog
Here are the required steps:
...
Choose the Principal Type - there are two choices currently:
...
...
(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 |
Add 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 credentials the add-on uses to derive temporary AWS security credentials for your Atlassian users, see Create individual users for getting started with this approach.
| Note | ||
|---|---|---|
| ||
| In order to use the Federated User Principal Type, you need to Grant an IAM Group Permission to Create Temporary Credentials! |
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. |
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:
...
Administration
Maintaining the Add-on
The following topics are applicable to regular add-on maintenance:
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
Managing AWS Resources
The following topics are applicable to AWS resource management:
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Configuring an AWS Connector
Refer to Configuring an AWS Connector for details.
The following topics are applicable to advanced scenarios only:
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
How-to Articles
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Frequently Asked Questions (FAQ)
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|