You turn on each export in the Kiro console. To use the console, you need the permissions in Policy: Allow administrators to configure Kiro and subscribe users.
Kiro has two places to set up exports:
- Controls. You set the exports in a policy. Your changes go to the policy's draft. Kiro uses them only after you publish the policy, and only for profiles that the policy is assigned to.
- Settings (deprecated). You set the exports in the Enable usage metrics logs dialog. Use it only if your organization doesn't use Controls yet.
The User activity report page in Controls holds every export setting. Open it before you follow the steps in the next sections.
- Sign in to the AWS console, and switch to the Kiro console.
- In the navigation pane, choose Controls, and then choose your policy.
- Choose Edit. Your changes save to the draft automatically.
- On the Rules and settings tab, go to Privacy and telemetry.
- Choose either the Kiro user activity reports row or the Kiro real-time user activity events row. Both open the User activity report page. Show in YAML in the row opens the YAML view instead.
The page shows a Destinations overview and one tab for each export: CSV report, OpenTelemetry metrics, and OpenTelemetry real-time events.
Each status in Destinations overview shows what the policy asks for, not whether data has arrived. For example, On, over the public internet means that the policy turns the export on.
Before you start, prepare the S3 bucket.
- Open the user activity report page, and choose the CSV report tab.
- In CSV report settings, choose Turn on.
- For CSV destination, enter the S3 URI with its prefix, for example
s3://amzn-s3-demo-bucket/user-activity-reports/. - Choose Save to draft. This also turns on Collect metrics per user, which every daily export needs.
- Choose Publish, and then confirm in the Publish changes? dialog.
Kiro writes the first report at the next 02:00 UTC. To confirm it, see Turn on the CSV report.
Before you start, create the AWS Key Management Service (AWS KMS) key and the metrics secret.
- Open the user activity report page, and choose the OpenTelemetry metrics tab.
- In Connection, choose Turn on.
- For OpenTelemetry credentials, paste the Amazon Resource Name (ARN) of your metrics secret.
- For OpenTelemetry protocol, choose gRPC or HTTP/protobuf. Use the protocol that your collector accepts. A wrong protocol causes no error, but no metrics arrive.
- For OpenTelemetry temporality, keep Delta, or choose Cumulative for a Prometheus-based collector such as Grafana Cloud.
- Choose Save to draft. This also turns on Collect metrics per user.
- If your collector is not on the public internet, follow steps 2 to 4 in Choose private connectivity now, so that Kiro never sends this export over the public internet.
- Test the connection in Test connection. Over the public internet, this sends a test record. With private connectivity, it only checks your setup.
- Choose Publish, and then confirm in the Publish changes? dialog.
- With private connectivity, allow up to about 10 minutes for AWS PrivateLink, or up to about 15 minutes for Amazon VPC Lattice, and then test again. This test sends a record over the private connection.
The first export runs at the next 00:30 UTC (02:00 UTC before November 26, 2026). It sends the previous day's metrics. Kiro doesn't send any data when you publish. To confirm the first export, see Confirm the export.
Before you start, create the events secret. It must be a different secret from the metrics secret. Real-time events don't need Collect metrics per user.
- Open the user activity report page, and choose the OpenTelemetry real-time events tab.
- In Connection, choose Turn on. In the dialog, Export real-time events to OpenTelemetry is already on.
- For Event export credentials, paste the ARN of your events secret.
- Choose Save to draft. The protocol is always OTLP logs over HTTP (http/protobuf).
- If your collector is not on the public internet, follow steps 2 to 4 in Choose private connectivity now, so that Kiro never sends this export over the public internet.
- Test the connection in Test connection. Over the public internet, this sends a test record. With private connectivity, it only checks your setup.
- Choose Publish, and then confirm in the Publish changes? dialog.
- With private connectivity, allow up to about 10 minutes for AWS PrivateLink, or up to about 15 minutes for Amazon VPC Lattice, and then test again. This test sends a record over the private connection.
Events start with the next user activity after you publish. Kiro doesn't send earlier activity. To confirm that events arrive, see Confirm the export.
Before you start, set up AWS PrivateLink or Amazon VPC Lattice, and put the private host in the secret.
- Open the user activity report page, and choose the OpenTelemetry metrics tab or the OpenTelemetry real-time events tab.
- In Private connectivity, choose Edit.
- For Private connectivity, choose AWS PrivateLink or Amazon VPC Lattice, and enter the fields for the mode:
- For AWS PrivateLink, enter the Endpoint service name and the Endpoint service Region. The Region must match the Region in the service name.
- For Amazon VPC Lattice, enter the resource configuration ARN in Lattice resource configuration, and the Collector hostname.
- Choose Save to draft.
- Choose Publish, and then confirm in the Publish changes? dialog. Kiro builds the private connection only after you publish.
- Allow up to about 10 minutes for AWS PrivateLink, or up to about 15 minutes for Amazon VPC Lattice. Then test the connection.
To go back to the public internet, set Private connectivity to Public internet, save, and publish.
In Controls, open the export's tab, choose Turn off, and publish. In Settings (deprecated), clear the export, and choose Enable.
Kiro keeps the saved values, such as the secret ARN and the private connectivity fields, so you can turn the export on again. With private connectivity, Kiro releases its VPC endpoint or Lattice association within about 5 minutes.
Turn on exports in the Kiro console