Configuring Amazon Kiro
Overview. Connect Amazon Kiro to LinearB to collect Kiro usage data and surface adoption and usage metrics in AI Analytics. Amazon Kiro integration is currently available in Closed Beta.. The generat…
Overview
Connect Amazon Kiro to LinearB to collect Kiro usage data and surface adoption and usage metrics in AI Analytics.
Before You Begin
Verify that you have the following:
- Company Admin access in LinearB.
- AWS administrative access to IAM, S3, and Identity Center.
- Amazon Kiro user activity reports enabled.
- The IAM Role ARN that LinearB will use.
- The S3 path containing Kiro usage reports.
- The Identity Store ID for your AWS Identity Center instance.
- The S3 bucket region.
- The Identity Center region.
Connect Amazon Kiro
- Navigate to Settings > Company Settings > AI Tracking.
- Select Amazon Kiro.
- Enter the following information:
- IAM Role ARN
- Usage Data S3 Path
- Identity Store ID
- S3 Bucket Region
- Identity Center Region
- Select Generate AWS Policies.
- Copy the generated Permissions Policy and Trust Policy.
- In AWS IAM, apply both policies to the role that LinearB will use.
- Return to LinearB and complete the connection.
Verify the Connection
After the connection is complete, LinearB validates access to the configured AWS resources.
When validation succeeds, Kiro usage data begins appearing in AI Analytics after reports are processed.
Troubleshooting
No Kiro Data Appears
Verify that the configured S3 path contains Kiro usage reports and that the path matches the report location configured in AWS.
Could Not Assume IAM Role
Verify that:
- The trust policy allows the LinearB AWS account.
- The External ID matches the value generated during setup.
- The IAM Role ARN is correct.
Bucket Not Found
Verify that the bucket name and configured region are correct.
Access Denied to S3
Verify that the role includes permissions to list and read objects from the configured bucket and prefix.
Identity Store Access Error
Verify that the role can access AWS Identity Store and that the Identity Store ID and region are correct.
Related Articles
How did we do?
Configuring Amazon Q Developer