Each day at 02:00 UTC, Kiro writes a CSV report of the previous day's activity to an Amazon S3 bucket in your account. Kiro writes one file for each Kiro client type, such as IDE and CLI. Each row describes one user on that day.
s3://bucketName/prefix/AWSLogs/accountId/KiroLogs/user_report/region/year/month/day/00/clientType_accountId_user_report_timestamp.csv
Create an Amazon S3 bucket for the reports. The bucket must meet these requirements:
- It is in the AWS Region of your Kiro profile. For more information, see Kiro profile and Supported Regions.
- It is in the AWS account where your users are subscribed. If users are subscribed in more than one account, create a bucket in each account. Kiro doesn't support cross-account buckets.
- It has a prefix, also called a folder. Kiro can't write to the root of a bucket.
- (Recommended) It is a different bucket from the one for prompt logging.
Add this bucket policy. Replace bucketName, prefix, region, and accountId with your values. The region and accountId in the Condition block must be the Region of your Kiro profile and the account where users are subscribed. To find the account ID, see Find your AWS account ID.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "KiroLogsWrite", "Effect": "Allow", "Principal": { "Service": "q.amazonaws.com" }, "Action": [ "s3:PutObject" ], "Resource": [ "arn:aws:s3:::bucketName/prefix/*" ], "Condition": { "StringEquals": { "aws:SourceAccount": "accountId" }, "ArnLike": { "aws:SourceArn": "arn:aws:codewhisperer:region:accountId:*" } } } ] }
To protect the data in the bucket, see Protecting data with encryption in the Amazon Simple Storage Service User Guide.
Turn on the report in the Kiro console. For the steps, see Turn on the CSV report.
Kiro writes the first report at the next 02:00 UTC after you turn it on. After that, Kiro writes a new report every day.
To confirm the first report, list s3://bucketName/prefix/AWSLogs/accountId/KiroLogs/user_report/ after 02:00 UTC. Expect one file for each client type that users used the day before. If no file arrives, see Troubleshooting.
You can query the reports with Amazon Athena, build dashboards in Amazon QuickSight, or load them into your own analytics pipeline.
Each report has static columns, then dynamic columns for each model and tool, then client-measured tool columns, and then four request-level columns. The dynamic columns depend on the models and tools that users used that day, so the position of a later column can change from day to day. Read columns by their header name, not by position.
| Column | Description |
|---|---|
Date | Date of the activity |
UserId | The user's IAM Identity Center user ID. If the profile signs in through an external identity provider, the user ID from that provider |
Client_Type | KIRO_IDE, KIRO_CLI, KIRO_WEB, KIRO_CREW, or PLUGIN. Other values can appear as Kiro adds clients |
Chat_Conversations | Number of conversations that the user had that day |
Credits_Used | Credits used from the user's subscription plan |
Overage_Cap | The overage limit set by the administrator, when Overage_Enabled is true. Otherwise, the credits included in the subscription plan |
Overage_Credits_Used | Overage credits used, when overage is enabled |
Overage_Enabled | Whether overage is enabled for the user: true or false |
ProfileId | The ARN of the Kiro profile of the activity |
Subscription_Tier | PRO, PRO_PLUS, PRO_MAX, POWER, or POOLING |
Total_Messages | Messages sent to and from Kiro, including user prompts, tool calls, and Kiro responses |
New_User | Whether the user activated their subscription that day |
User_Email | The user's email address. With an external identity provider that has no email address for the user, the user name |
Usage_Limit | The user's credit limit. 999999 for a shared-pool user with no individual limit |
*model_name*_messages | Messages processed by the model for the user, including Auto |
*model_name*_credits | Credits used by the model for the user. Credits that Kiro can't attribute to a model are in unallocated_credits |
*tool_name*_tool_calls | Number of times the model asked for the tool for the user |
*_client columns | Tool calls that the Kiro client ran, with their outcomes and durations. See Client-measured tool columns |
Client_Version | Kiro client versions that the user sent requests from, separated by ;. Empty when Kiro recorded no version |
Requests_With_Tools | Requests in which the agent called at least one tool |
Answers_Cut_Off | Answers that stopped because the response reached the model's output length limit |
Avg_Response_Ms | Average response time in milliseconds, from when Kiro received the request to the end of the response. 0 when the user had no timed requests |
The number of *model_name*_messages, *model_name*_credits, and *tool_name*_tool_calls columns depends on the models and tools that any user used that day.
- Kiro sorts each family of columns by name.
- In model columns, hyphens become underscores. For example,
claude-sonnet-4-5becomesclaude_sonnet_4_5_messagesandclaude_sonnet_4_5_credits. - Kiro uses tool names as they are.
- A column contains
0when the user didn't use that model or tool that day. - Internal models that Kiro uses for its own processing are left out of the
*model_name*_messagescolumns and ofTotal_Messages.
The *tool_name*_tool_calls columns count the tools that the model asked for. The columns that end in _client count the tool calls that the Kiro client ran and reported. The client sends this data only from supported versions. See Client versions.
| Column | Description |
|---|---|
*tool_name*_tool_calls_client | Tool calls that the client ran, for each tool |
*tool_name*_tool_errors_client | Tool call errors, for each tool |
*tool_name*_tool_duration_ms_avg_client | Average tool call duration in milliseconds, for each tool |
*kind*_tool_calls_by_kind_client | Tool calls for each tool kind, such as builtin, mcp, or skill |
*kind*_tool_duration_by_kind_ms_avg_client | Average tool call duration in milliseconds, for each tool kind |
*outcome*_tool_calls_by_outcome_client | Tool calls for each outcome, such as completed or abort |
*errorType*_tool_errors_by_type_client | Tool call errors for each error type |
*server*_mcp_server_calls_client | Tool calls for each MCP server |
*server*_mcp_server_errors_client | Tool call errors for each MCP server |
*server*_mcp_server_duration_ms_avg_client | Average tool call duration in milliseconds, for each MCP server |
*skill*_skill_calls_client | Skill loads for each skill |
*mode*_tool_calls_by_agent_mode_client | Tool calls for each agent mode, such as vibe or spec |
Each value of the placeholder that occurs on that day gets its own column. These rules apply:
- Kind, outcome, and agent mode values are lowercase. Tool names and MCP server names keep their case.
- A tool call with the outcome
UNKNOWNis not counted. - An agent mode that Kiro doesn't recognize counts as
unknown. - A failed tool call with no error type counts as
unknown.
For the real-time event attribute behind each column, see How events map to daily data.
Kiro also writes a legacy user activity report to the same bucket, in the by_user_analytic path. For its location and metrics, see Legacy user activity report.
Export CSV reports to Amazon S3