New in this release
- Support for the AWS GovCloud (US) Region (experimental)
Fixed in this release
- Exception on connector save when using a PostgreSQL backend
- Exception on add-on initialization when using a MySQL backend
This app has been archived
You may still get support information and download previous versions of this app. Learn more.
Last modified 2015-04-09 • 268 downloads • By Utoolity
Support
To check known issues (or if you want to file one), view this app's issue tracker.
To learn more about the app, you should:
- Read the documentation.
This is a supported app, so you may contact the vendor (or support contact) for help:
Description
Federated AWS access for Atlassian users
Add long-term AWS security credentials (IAM users) once, configure AWS access for Atlassian groups with temporary credentials and fine grained permissions via IAM Policies thereafter (Identity Broker).
Single Sign-On (SSO) to the AWS Management Console
Access AWS resources directly via menu links and/or a configurable 'AWS Management Console Login' gadget.
REST API for temporary AWS Security Credentials
Expose AWS Connectors to requesting users with sufficient permissions and allow retrieval of temporary AWS security credentials based on such connectors (Token Vendor).
More details
+++ NOTE: This add-on is deprecated and superseded by Identity Federation for AWS (Jira) and Identity Federation for AWS (Bamboo) for technical reasons (existing customers are eligible for free cross upgrades). +++
Integrate AWS into your Jira and DevOps workflows (Identity Broker/Token Vendor):
- Secure your AWS credentials – store long-term AWS security credentials with industry standard encryption without exposing them to your users (or add-ons).
- Empower your Atlassian users – provide Single Sign-On (SSO) to the AWS Management Console.
- Integrate tailored AWS resources – use the REST API to provision AWS resources based on the Atlassian user name (e.g. a dedicated Amazon S3 bucket or EC2 instance per developer).
- Forget about distributing or revoking AWS credentials – grant fine grained permissions for AWS resources to Atlassian users based on one or few sets of long-term AWS security credentials only.
Version history
1.2.1Jira Server 5.1 - 6.4.142013-11-02Adds support for the AWS GovCloud (US) Region; fixes two database specific bugs 1.2.0Jira Server 5.1 - 6.4.142013-08-01Adds configurable credentials expiration to further increase control over your security footprint. Release 1.2.0 adds configurable credentials expiration:
- Configurable credentials expiration
Configure the expiration time of granted temporary security credentials to further increase control over your security footprint - an administrator can configure the maximum number of seconds temporary credentials based on a connector are valid, any client can either use this maximum or further reduce it even.
- Configurable credentials expiration
1.1.1Jira Server 5.1 - 6.0.82013-06-04Fixes the issue collector link causing a horizontal scrollbar and addresses an internal shortcoming to ease subsequent API documentation. Release 1.1.0 adds a second principal type Account (IAM User) to expand the available integration scenarios, significantly improves Atlassian Design Guidelines (ADG) compliance and adds sample IAM Policies to ease getting started:
- Second Principal Type Account (IAM User)
Use temporary credentials for a configured IAM user or AWS account itself to enable both simplified integration scenarios as well as previously unavailable services (AWS CloudFormation, Amazon Elastic MapReduce, AWS Elastic Beanstalk). - Improved Atlassian Design Guidelines compliance
The initial user interface has been revised to significantly improve Atlassian Design Guidelines (ADG) compliance. - Sample IAM Policies
The configuration dialog now offers a few example Identity and Access Management (IAM) Policies to ease getting started.
- Release 1.1.1 fixes the issue collector link causing a horizontal scrollbar and addresses an internal shortcoming to ease subsequent API documentation.
- Second Principal Type Account (IAM User)
1.1.0Jira Server 5.1 - 6.0.82013-05-31Adds a second principal type Account (IAM User) to expand the available integration scenarios, significantly improves Atlassian Design Guidelines (ADG) compliance and adds sample IAM Policies to ease getting started. Release 1.1.0 adds a second principal type Account (IAM User) to expand the available integration scenarios, significantly improves Atlassian Design Guidelines (ADG) compliance and adds sample IAM Policies to ease getting started:- Second Principal Type Account (IAM User)
Use temporary credentials for a configured IAM user or AWS account itself to enable both simplified integration scenarios as well as previously unavailable services (AWS CloudFormation, Amazon Elastic MapReduce, AWS Elastic Beanstalk). - Improved Atlassian Design Guidelines compliance
The initial user interface has been revised to significantly improve Atlassian Design Guidelines (ADG) compliance. - Sample IAM Policies
The configuration dialog now offers a few example Identity and Access Management (IAM) Policies to ease getting started.
- Second Principal Type Account (IAM User)
1.0.0Jira Server 5.1 - 6.0.82013-05-20Initial release This is the initial release 1.0.0 - it provides configuration of AWS Connectors (map IAM users and policies to Atlassian groups), Single Sign-On (SSO) to the AWS Management Console via menu links and/or a configurable AWS Management Console Login Gadget and a REST API for temporary AWS credentials.