Documentation for Identity Federation for AWS 1.0 – other releases are available in the Identity Federation for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Identity Federation for AWS is mainly a system integration and API Add-on that provides Temporary 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 Security Credential Variations

At the moment the Add-on supports Temporary Security Credentials to Enable Access for Federated Users, support for Temporary Security Credentials for Delegating API Access might be added later on.

On this page:

AWS Connector Management

In order to enable the desired access to your AWS resources you need to configure at least one AWS Connector. You can access this functionality via the AWS Connector management screen:

Adding an account (IAM user)

An account resp. IAM User provides the required secret credentials which the Add-on uses to derive the temporary AWS credentials for your Atlassian users, see Create individual users for getting started with this approach.

Required IAM Permissions

You need to Grant an IAM Group Permission to Create Temporary Credentials to facilitate this Add-ons functionality!

Accounts are added/edited/deleted inline while adding/editing an AWS Connector. All fields are required, you can select an arbitrary name according to your needs.

Editing an existing account will change it for all AWS Connectors using it.

 

Configuring an AWS Connector with 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 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).

  • No labels