Use the AWS Resource link to create deep links with optional single sign-on (SSO) to the AWS Management Console.
Usage
To use the AWS Resource link for the creation of deep links with optional single sign-on (SSO):
- (Optional) Configure a new AWS Connector with a Principal Type of Assume Role or Federated User (other principal types do not support SSO)
- In the Jira issue editor, choose More > Link
- Find and select the AWS Resource link
(Optional) Complete the following settings:
Resource URL Specify the resource URL
Identify deep link patterns with the AWS Resource Groups editor
You can copy most links as is from an AWS Management Console view that suits your needs – the AWS Resource Groups editor is particularly well suited to identify useful deep link patterns.
Link Text Specify the link text
Connector (Optional) Select an AWS Connector to enable SSO – skip to use the configured resource URL without SSO
Comment (Optional) Add a regular Jira issue comment - Click Insert to create the link
To access the AWS Management Console via SSO, click the resulting deep link to AWS services and resources.
AWS account session affinity
The AWS Management Console is session aware and will prompt you to log out of the current account first, if you click on a link that targets a different account. In order to access different AWS accounts at the same time, you need to access the AWS Management Console from independent browser sessions, for example via the common 'incognito' or 'private' browser windows.
How-to Articles
Frequently Asked Questions (FAQ)
Atlassian account required