Configuring Amazon Q Developer

Overview

LinearB integrates with Amazon Q Developer to collect Amazon Q Developer user activity reports and surface usage and adoption signals in AI Analytics and related AI reporting views.

This integration connects LinearB to Amazon Q Developer usage reports in your AWS environment. During setup, you provide your AWS details, generate the required policies, apply them in AWS, and then complete the connection in LinearB.

Before You Begin

• LinearB role: Company Admin
• AWS access: AWS admin access for IAM, S3, and Identity Center configuration
• Amazon Q requirement: Amazon Q Developer user activity reports enabled in your AWS environment

Before starting the setup in LinearB, make sure you can access the following details:

• IAM Role ARN for the cross-account role LinearB will assume
• Usage Data S3 Path where Amazon Q Developer user activity reports are exported
• Identity Store ID for your AWS Identity Center instance
• S3 Bucket Region
• Identity Center Region

Step 1 — Open Amazon Q Settings in LinearB

1. Go to Settings → Company Settings → AI Tracking → Amazon Q.
2. In the Amazon Q Developer Integration section, review the setup requirements.
3. Use Go to Documentation if you need the setup guide while completing the form.

Step 2 — Enter Your AWS Details

In the setup form, enter the AWS environment details where Amazon Q Developer is configured:

• IAM Role ARN — The cross-account IAM role that LinearB will assume
• Usage Data S3 Path — The S3 path where Amazon Q usage reports are exported
• Identity Store ID — The Identity Store ID where Amazon Q users are configured
• S3 Bucket Region — The AWS region for the S3 bucket
• Identity Center Region — The AWS region for IAM Identity Center

After entering these values, click Generate AWS Policies.

Step 3 — Generate the AWS Policies

LinearB generates the required AWS policies based on your configuration. The setup dialog includes:

• Permissions Policy — Attach this to the IAM role so LinearB can read the required S3 resources and Identity Store data
• Trust Policy — Attach this to the IAM role so LinearB can assume the role using the generated AWS Account ID and External ID

Use the copy controls in the dialog to copy each policy into your AWS IAM console.

Step 4 — Apply the Policies in AWS

1. Open your AWS IAM console.
2. Locate the IAM role you want LinearB to use.
3. Attach the generated Permissions Policy to the role.
4. Update the role’s Trust Policy with the generated LinearB AWS Account ID and External ID.
5. Save your changes in AWS.

The generated policy set is designed to grant LinearB read-only access to the required Amazon Q reporting resources and the relevant Identity Store data needed for user resolution.

Step 5 — Connect Amazon Q

Return to LinearB and click Connect Amazon Q.

During validation, LinearB attempts to assume the IAM role and verify access to the configured S3 path and Identity Store information.

Connection Status and Validation

During setup, you may see one of the following states:

• Connecting — LinearB is validating your AWS configuration and testing access.
• Error — One or more validation checks failed. Review the error message, correct the configuration, and retry.
• Success — LinearB successfully validated the configuration and connected Amazon Q Developer.

Once connected, LinearB can begin ingesting Amazon Q Developer usage activity for reporting.

Expected Data Behavior

• Amazon Q Developer user activity reports are generated daily in your AWS environment.
• LinearB reads the configured S3 path to collect available Amazon Q usage reports.
• Usage reporting depends on the reports available in the configured bucket and prefix.
• User resolution depends on access to the configured AWS Identity Store.

Troubleshooting

Invalid Role ARN

The IAM Role ARN doesn’t look valid. Please verify you copied the full ARN from the AWS console. It should match this format:

arn:aws:iam::<account-id>:role/<role-name>

Invalid S3 URI format

The S3 bucket is not in a valid format or includes invalid characters.

Couldn’t assume IAM Role

We were unable to assume the IAM role in your AWS account. Verify the following:

• The role trust policy allows the LinearB AWS account as a principal
• The sts:ExternalId in the trust policy exactly matches the External ID shown in the LinearB setup window
• You used the correct IAM Role ARN

IAM Role not found

AWS reports that the specified IAM Role ARN does not exist. Confirm that you copied the ARN from the correct AWS account and region.

Temporary AWS issue

We couldn’t complete the connection test due to a temporary AWS STS error such as throttling or service unavailability. Try again in a few minutes. If the issue persists, contact your AWS administrator.

Bucket does not exist or bucket name is incorrect

If the configured bucket cannot be found, LinearB will report that the S3 bucket does not exist in the configured region. Check the bucket name and region, then try again.

No permission to list S3 bucket

If LinearB can assume the IAM role but cannot list objects in the bucket, update the role policy to allow s3:ListBucket for the configured bucket and prefix.

No permission to read S3 objects

If LinearB can see the bucket but cannot read the Amazon Q report files under the configured prefix, update the role policy to allow s3:GetObject on the relevant Amazon Q path.

Incorrect S3 region

If the configured S3 region does not match the bucket’s actual region, update the S3 region to match the bucket’s region and try again.

IAM Identity Center not found in region

If no IAM Identity Center instance exists in the configured region, verify the Identity Center home region in AWS and update the setting. If needed, contact your AWS administrator.

Access denied to Identity Store

If LinearB can assume the IAM role but cannot read from Identity Store, update the role to allow identitystore:GetUser and identitystore:DescribeUser.

Where Amazon Q Data Appears

After data is collected and processed, Amazon Q usage data may appear in the following LinearB areas, where supported:

• AI Analytics
• AI Adoption
• AI Insights

Known Limitations

• Amazon Q Developer integration is currently available in Closed Beta.
• To remove or reconfigure the integration, contact support@linearb.io.
• The generated policy files are temporary and tied to the current setup window.
• If you close the setup window before completing the connection, you must regenerate the policies and use the new values.
• Data availability depends on the Amazon Q Developer reports available in the configured S3 path.

Related Articles

• AI Analytics: Adoption, Workflow, and Impact
• AI Adoption
• AI Insights – Overview