| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Principal Type | AWS Documentation | API action | Notes |
|---|---|---|---|
 Federated User Federated User | Temporary Security Credentials to Enable Access for Federated Users | GetFederationToken | |
| IAM User | Temporary Security Credentials to Enable Access for IAM Users | GetSessionToken | |
 IAM Role | Temporary Security Credentials for Delegating API Access | AssumeRole | Support for IAM roles is on our roadmap, see UAA-32 for details |
 SAML Federation | Temporary Security Credentials for SAML Federation | AssumeRoleWithSAML | Support for SAML is not on our roadmap, see the FAQ for details |
...
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:
Create/Edit Connector
Clicking Create Connector (or Edit later on) opens the Edit AWS Connector dialog:
...
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).
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:
...