Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Configuring Jira Cloud connections

Focus mode
Configuring Jira Cloud connections - AWS Glue

Jira Cloud supports the AUTHORIZATION_CODE grant type for OAuth2.

  • This grant type is considered "three-legged" OAuth as it relies on redirecting users to a third-party authorization server to authenticate the user. It is used when creating connections via the AWS Glue console. The AWS Glue console will redirect the user to Jira Cloud where the user must login and allow AWS Glue the requested permissions to access their Jira Cloud instance.

  • Users may still opt to create their own connected app in Jira Cloud and provide their own client ID and client secret when creating connections through the AWS Glue console. In this scenario, they will still be redirected to Jira Cloud to login and authorize AWS Glue to access their resources.

  • This grant type results in a refresh token and access token. The access token is short lived, and may be refreshed automatically without user interaction using the refresh token.

  • For public Jira Cloud documentation on creating a connected app for Authorization Code OAuth flow, see Enabling OAuth 2.0 (3LO).

To configure a Jira Cloud connection:

  1. In AWS Secrets Manager, create a secret with the following details:

    1. For the customer managed connected app, the Secret should contain the connected app Consumer Secret with USER_MANAGED_CLIENT_APPLICATION_CLIENT_SECRET as key.

    2. Note: You must create a secret for the connection in AWS Glue.

  2. In AWS Glue Glue Studio, create a connection under Data Connections by following the steps below:

    1. When selecting a Connection type, select Jira Cloud.

    2. Provide the Jira Cloud environment.

    3. Select the AWS IAM role which AWS Glue can assume and has permissions for following actions:

      { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "secretsmanager:DescribeSecret", "secretsmanager:GetSecretValue", "secretsmanager:PutSecretValue", "ec2:CreateNetworkInterface", "ec2:DescribeNetworkInterface", "ec2:DeleteNetworkInterface", ], "Resource": "*" } ] }
    4. Select the secretName which you want to use for this connection in AWS Glue to put the tokens.

    5. Select the network options if you want to use your network.

  3. Grant the IAM role associated with your AWS Glue job permission to read secretName.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.