Identity Federation for AWS is a foundational Amazon Web Services (AWS) integration add-on that provides Temporary AWS 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.
Temporary AWS Security Credentials Variations
At the moment the add-on supports the following two Principal Types:
- 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.
On this page:
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:
- Select the account to use (you might need to add accounts first)
- Choose this Connector's name
Choose the Principal Type - there are two choices currently:
Principal Type Explanation Learn more at AWS Federated User Yields temporary AWS security credentials for a federated user with the Atlassian user name and an optional IAM policy (if absent, AWS applies a default)
In order to use the Federated User Principal Type, you need to Grant an IAM Group Permission to Create Temporary Credentials!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
Grant an IAM Group Permission to Create Temporary Credentials
Account (IAM User) Yields temporary AWS security credentials for the selected IAM user (recommended) or AWS account (disadvised) itself
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 - (Optional) Add an IAM Policy (only available for Principal Type Federated User
(Optional) Grant the permission to use this Connector to one or more of your JRIA groups
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.
Required IAM Permissions
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.
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:
