Skip to main content

Troubleshoot user activity exports

Kiro doesn't send failure notifications. Start with Test the connection. The test names the cause of most configuration errors. Then use the checks on this page.

Check the basics

  1. The policy is published. In Controls, changes apply only after you choose Publish. Under Destinations overview, the export's status should start with On, such as On, over the public internet.
  2. The policy is assigned. Kiro applies the policy only to profiles that it is assigned to.
  3. Users are active. Kiro sends real-time events only when users work in Kiro. Daily exports cover only users who were active on that day.
  4. The first daily export has run. Kiro sends the CSV report at 02:00 UTC, and OpenTelemetry metrics at 00:30 UTC (02:00 UTC before November 26, 2026). Each covers the previous day.

No CSV report arrives

CauseFix
The bucket is not in the Kiro profile's Region or accountCreate the bucket in the profile's Region and in the account where users are subscribed
The bucket policy doesn't let q.amazonaws.com writeAdd the bucket policy. Check that aws:SourceAccount and aws:SourceArn match your account and Region
The S3 URI has no prefixAdd a prefix. Kiro can't write to the root of a bucket

No OpenTelemetry metrics arrive

Check these causes in order:

  1. Region or account. The secret and its AWS Key Management Service (AWS KMS) key must be in the same account and Region as your Kiro profile.
  2. Missing permission. q.amazonaws.com needs secretsmanager:GetSecretValue on the secret, and kms:Decrypt and kms:DescribeKey on the key. Granting only one of them fails the same way as granting neither.
  3. Wrong protocol. gRPC to an HTTP-only endpoint, or HTTP/protobuf to a gRPC-only endpoint, fails with no error. Grafana Cloud, Datadog, and Amazon CloudWatch need HTTP/protobuf.
  4. Wrong temporality. Grafana Cloud rejects delta metrics. Choose Cumulative.
  5. Malformed header. Use one header in Name=value format. For a base64 credential, the decoded value has exactly one :.
  6. Amazon CloudWatch only. The metrics are in the account that issued the API key. They don't appear in the classic metrics console. Query them with PromQL.
  7. Datapoints too old. Before November 26, 2026, the daily metrics arrive about two hours old. Dynatrace and Grafana Cloud reject them as too old. Until then, use real-time events for these platforms, or fill the gap from the CSV report. See Check your platform's time window.

No real-time events arrive

Check these causes in order:

  1. Region or account. The secret and its KMS key must be in the same account and Region as your Kiro profile.
  2. Missing permission. q.amazonaws.com needs a grant on both the secret and the key.
  3. The metrics secret was used. The events secret must point to your collector's logs base URL, not to a metrics URL such as https://otlp.datadoghq.com/v1/metrics.
  4. Wrong path. Give the base URL. Kiro adds /v1/logs. For Grafana Cloud, the base URL ends in /otlp.
  5. Malformed header. Use comma-separated Name=value pairs, with no comma inside a value. CloudWatch Logs needs all three headers.
  6. CloudWatch Logs only. Check that the log group and log stream exist. Bearer token authentication must be on for the log group. The API key must come from the account that owns the log group.
  7. Wrong Dynatrace prefix. Use Api-Token with an access token, and Bearer with a platform token.

No tool call data arrives

kiro.chat.message events arrive, but kiro.tool.call events don't, or the _client CSV columns and metrics are empty.

CauseFix
The client is too oldUpdate Kiro IDE to the latest release. Update Kiro CLI to 3.0.0 or later, or to 3.1.0 or later when Collect metrics per user is off. See Client versions
An old process is still runningQuit every IDE window and kiro-cli process, and start them again
Kiro CLI uses the V2 agent engineRun kiro-cli settings chat.agentEngine v3
The prompts didn't use toolsSend a prompt that reads a file or runs a command

Private connectivity

Test results

When the private connection is not ready, the test sends nothing, and the result shows Endpoint not ready yet or Connection not ready yet. The detail message tells you why.

Detail starts withMeaningWhat to do
"Kiro has not set up a private connection to endpoint service …"Kiro has no connection for this endpoint service. Usually Kiro's account is not an allowed principal. Waiting doesn't helpAsk your vendor, or the owner of your own endpoint service, to allow Kiro's account. Then publish again
"This profile is not using Kiro's private connection to endpoint service …"The published policy doesn't select this endpoint servicePublish private connectivity with this endpoint service, and turn on the export
"Kiro's private connection to this endpoint service was set up in …"The Region in the test differs from the published RegionCorrect Endpoint service Region
"Kiro is still creating …", "… is still being set up", "… does not have a private DNS name yet", or "… is in its warm-up period"The connection is being builtTest again. The connection can take up to about 10 minutes after you publish with AWS PrivateLink, or 15 minutes with Amazon VPC Lattice. If it doesn't clear, check that the endpoint service owner accepted the connection and that the service has a private DNS name
"Kiro's private connection to this endpoint service is in state …"The endpoint service owner rejected the connection, or it failed. Waiting doesn't helpAsk the endpoint service owner to check Kiro's connection request
"Kiro has not set up a private connection to resource configuration …"Kiro has no connection for this resource configurationShare the resource configuration with Kiro, then publish again
"Kiro has not connected to resource configuration …"Kiro didn't find your resource shareCheck the share's Region, account ID, and resource configuration
"Resource configuration … is connected under a different collector hostname …"The test hostname differs from the published hostnameUse the published hostname. To change it, see Behavior and limits
"Kiro's connection to resource configuration … failed and is being replaced"The association failed. Waiting doesn't helpCheck the resource configuration and its resource gateway, then publish again
"Kiro's connection to resource configuration … is active, but … is not resolvable …"DNS for your hostname is not ready in Kiro's network yetTest again in a minute
"Kiro has not built the private connection yet, so nothing was sent …"You tested a private mode before you publishedPublish, and test again when the connection is ready, up to about 10 minutes after you publish with AWS PrivateLink, or 15 minutes with Amazon VPC Lattice
"Kiro checked your setup and found nothing missing …"You tested before you published. Your setup looks complete, and Kiro hasn't built the connection yetPublish, and test again when the connection is ready, up to about 10 minutes after you publish with AWS PrivateLink, or 15 minutes with Amazon VPC Lattice
"Kiro's AWS account cannot see endpoint service …"Kiro's account is not an allowed principal of the endpoint service, or the name is wrong. Waiting doesn't helpCheck the name. Ask the endpoint service owner to allow Kiro's account, then publish again
"Kiro could not confirm that the endpoint service has a verified private DNS name …"The endpoint service may have no private DNS name, or the name is not verified yetAsk the endpoint service owner to set and verify the private DNS name, then publish
"Resource configuration … is not shared with Kiro's AWS account, or the share invitation expired …"Kiro didn't find your AWS RAM shareShare the resource configuration with Kiro's account, then publish within 12 hours
"Kiro cannot tell how long your private connection has been available"Kiro can't confirm that the endpoint's warm-up period is overTest again. The connection can take up to about 10 minutes after you publish to become ready
"Kiro cannot create the private connection: … does not offer any availability zone …"The endpoint service has no Availability Zone that Kiro can use in your Region. Waiting doesn't helpAsk the endpoint service owner to add Availability Zones to the service, then publish again
"… endpoint service is not available to Kiro's AWS account"Kiro's account can't use the endpoint service. Waiting doesn't helpAsk the endpoint service owner to allow Kiro's account, then publish again
"Resource configuration … is not owned by this profile's AWS account"The resource configuration belongs to another accountCreate and share the resource configuration from the account that holds your Kiro profile, then publish again
"Collector hostname … cannot be used for private connectivity"The hostname breaks a hostname rule, for example it has a vpce labelChoose a hostname that meets the rules in Choose the collector hostname, then publish again
A detail that says the Amazon VPC Lattice connection is in its warm-up periodThe association is active, and Kiro is waiting before it sendsTest again. The connection can take up to about 15 minutes after you publish to become ready
"Testing a private connection is not available in this Region yet."Kiro can't run a private test in this RegionCheck that data arrives at your collector

Symptoms

SymptomCauseFix
AWS PrivateLink: TLS errors, or no dataThe secret uses the collector's public hostname or a vpce.amazonaws.com nameUse the endpoint service's private DNS name
AWS PrivateLink: never readyKiro's account is not allowed, the endpoint service owner didn't accept the connection, or the service has no private DNS nameAsk the endpoint service owner to check all three, then publish again
AWS PrivateLink: the vendor has no private DNS nameThe vendor expects a private hosted zone in your VPC, which Kiro can't useRun your own collector, share it through Amazon VPC Lattice, and forward the data to your vendor
AWS PrivateLink, cross-Region: never readyThe endpoint service doesn't support your profile's Region, or it is in another AWS partitionAsk the endpoint service owner to add your Region to the service
Amazon VPC Lattice: never readyThe share names the wrong account, is in the wrong Region, came after you published, or comes from an account that doesn't own the resource configurationShare from the owning account to Kiro's account for your Region, then publish again
Amazon VPC Lattice: never ready, and you published more than 12 hours after you created the shareThe share invitation expiredAdd Kiro's account to the share again, and publish within 12 hours
Amazon VPC Lattice: never ready, and you published a correct share within 12 hoursAnother Kiro customer already uses the collector hostnameChoose a hostname in your own domain. Turn off the export, publish, wait about 5 minutes, and then publish the export with the new hostname. Switch to Public internet instead only if your network rules allow it. See Behavior and limits
Amazon VPC Lattice: deliveries time outThe port is not 443, 4317, or 4318, or a security group blocks itSee Choose a collector port and Security groups
Amazon VPC Lattice: TLS errorsThe certificate is self-signed, from a private certificate authority, or doesn't cover the hostnameSee Use a private certificate authority
Amazon VPC Lattice: data stops after you change the secretThe host in the secret no longer matches Collector hostname. Kiro compares them before each delivery, and sends nothing when they differUse the same hostname in both. To change the hostname, see Behavior and limits
A load balancer in front of the collector returns errorsThe protocol doesn't match the target groupFor gRPC, use protocol version gRPC. For HTTP, use HTTP1 or HTTP2
The test says "Kiro did not send the test. OTEL_EXPORTER_OTLP_ENDPOINT must be an https:// URL …"The secret's endpoint starts with http://, or its host is an internal IP address or a one-word nameUse an https:// URL that your certificate covers
Page updated: November 16, 2026