Over the public internet, Test connection sends one test record to your collector with the values in the policy draft. With private connectivity, it checks your setup before you publish and sends a record after the private connection is ready. Nothing is saved, and no usage data is sent. Use it to find a wrong endpoint, credential, or protocol before the first export. Turn on the export in the draft before you test it.
In Controls, each OpenTelemetry tab of the User activity report page has a Test connection section. In Settings (deprecated), Test connection is in the Enable usage metrics logs dialog. To open the page, see Open the user activity report page.
| Connectivity | What the test uses | When to test |
|---|---|---|
| Public internet | The values in the draft | Any time, also before you publish |
| AWS PrivateLink | Before you publish: a check of your setup. After you publish: the private connection that Kiro built | Before you publish, to find a missing step. Then after you publish, when the connection is ready. That can take up to about 10 minutes |
| Amazon VPC Lattice | Before you publish: a check of your setup. After you publish: the private connection that Kiro built | Before you publish, to find a missing step. Then after you publish, when the connection is ready. That can take up to about 15 minutes |
Before you publish, a private test sends nothing. Kiro only reads your setup and names the first missing step:
- AWS PrivateLink: Kiro's account can see the endpoint service, and the service has a verified private DNS name.
- Amazon VPC Lattice: the resource configuration is shared with Kiro's account.
- Both: Kiro can read the secret. For Amazon VPC Lattice, the secret's endpoint uses the collector hostname.
When every check passes, the detail message starts with "Kiro checked your setup and found nothing missing". Publish, wait for the connection to become ready, up to about 10 minutes for AWS PrivateLink or 15 minutes for Amazon VPC Lattice, and test again to send a test record.
The test record looks like a real record. It has the same resource attributes, such as service.name = kiro-enterprise. It also has attributes that mark it as a test:
| Attribute | Metrics test | Events test |
|---|---|---|
| Record | One datapoint with value 1, in the metric kiro.test.connection | One log record with eventName = kiro.test.connection |
kiro.test | true | true |
kiro.test.signal | metrics | events |
kiro.test.id | Not sent. A metric attribute that changes on each test would add a new series to your backend | An ID for this test |
The metrics test uses its own metric name, outside kiro.daily.*, so it doesn't change your daily totals. To keep test events out of your dashboards and alerts, filter on kiro.event.name != "kiro.test.connection".
The console shows Connection successful when the test passes. A passed test means that your collector accepted one test record over the path that you chose. It doesn't prove that usage data will arrive:
- The export still needs to be published.
- Kiro sends events only when your users are active, and metrics once a day at 00:30 UTC (02:00 UTC before November 26, 2026).
- Some collectors accept a request and then drop the records in it. Always check the data at the destination.
When the test fails, the console shows one of these results. A failed test also shows a Test ID. Give it to AWS Support if you contact them.
| What the console shows | What it means | What to do |
|---|---|---|
| Could not run the test, with a message such as "OTel exporter configuration requires a valid Secrets Manager secret ARN" | Kiro checked the secret ARN before the test and rejected it. Nothing was called. Other messages say that the secret must belong to the profile's AWS account, or must be in the profile's Region | Paste the full ARN of a secret in the same account and Region as your Kiro profile |
| Connection failed: "Kiro could not read the secret. Check all three: …" | Kiro can't read the secret, or the secret has no endpoint. The message lists three checks. The secret uses a customer managed AWS Key Management Service (AWS KMS) key, not aws/secretsmanager. The key policy grants Kiro kms:Decrypt and kms:DescribeKey. The secret's resource policy grants Kiro secretsmanager:GetSecretValue | Check the KMS key policy, the secret's resource policy, and the secret's JSON. See Prepare credentials |
| Connection failed: "Kiro did not send the test. OTEL_EXPORTER_OTLP_ENDPOINT must be an https:// URL with a domain name or public IP address, and no credentials." | Kiro rejected the endpoint before it sent anything. The URL is not https://, has credentials in it, or its host is an internal IP address or a one-word name such as localhost. A private DNS name for AWS PrivateLink or Amazon VPC Lattice is accepted | Use an https:// URL whose host is a domain name or a public IP address |
| Connection failed: "Kiro did not send the test: it could not read OTEL_EXPORTER_OTLP_HEADERS in the secret." | Kiro can't parse OTEL_EXPORTER_OTLP_HEADERS, or it names a header that Kiro reserves, such as Host or Content-Type. Nothing was sent | Metrics: use one HeaderName=value. Events: use comma-separated HeaderName=value pairs, with no reserved headers |
| Connection failed: "Kiro sent the test event, but the collector did not accept it." For metrics, the message says "test datapoint" | Kiro sent the record, and your collector didn't accept it. For example, the host is unreachable, the request timed out, TLS failed, or the collector returned 401 or 403 | Check the credential in OTEL_EXPORTER_OTLP_HEADERS first. Then check that the endpoint is right and reachable. For events, check that the collector accepts OTLP logs over HTTP. For metrics, check the protocol, and the temporality if the form shows it. See Troubleshooting |
| Endpoint not ready yet (AWS PrivateLink) or Connection not ready yet (Amazon VPC Lattice), with a detail message | You chose a private mode, and Kiro's private connection is not ready. Nothing was sent | Expected for up to about 10 minutes after you publish with AWS PrivateLink, or 15 minutes with Amazon VPC Lattice. Test again later. If it doesn't clear, read the detail message and see Private connectivity errors |
| Could not run the test: "Private connectivity is not available for this AWS account yet, so Kiro did not run the test. To check the collector now, set Private connectivity to Public internet and test again." In Settings (deprecated), the message is "OTel private connectivity is not enabled for this account" | Private connectivity isn't available for this AWS account yet. This is not a collector configuration error. Nothing was sent | If your network rules allow public delivery, test over Public internet. To use private connectivity, contact AWS Support |
| Connection failed: "Kiro could not complete the test. Try again in a moment. If it keeps happening, contact support with the test ID below." | A fault on Kiro's side | Try again in a moment. If it keeps happening, contact AWS Support with the Test ID |
| Too many tests: "Connection tests are rate limited. Wait a few seconds and try again — this is not a problem with your configuration." | You ran tests faster than Kiro allows | Wait a few seconds and test again |
A passed test shows the endpoint that Kiro delivered to, so you can confirm the URL.
Test the connection