Answer: You need to create a symmetric customer managed AWS KMS key (not the default aws/secretsmanager key) and select that key as the encryption key when you create the Secrets Manager secret. The KMS key, Secrets Manager secret, and Kiro profile must be in the same AWS Region. Status: Check failed Entry: tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup Revision: 1 Digest: sha256:c9d1d34322e2ef6f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:41:11Z Last changed: 2026-11-13T03:41:11Z Last verified: 2026-11-16T13:09:30Z Last attempt: 2026-11-20T13:26:59Z (failed) Next check: 2026-11-20T14:26:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of KMS key type | symmetric customer managed AWS KMS key | [1] | 2026-11-16 Default key restriction | aws/secretsmanager | [1] | 2026-11-16 Region requirement | same AWS Region | [1] | 2026-11-16 Service principal | q.amazonaws.com | [1] | 2026-11-16 Secret encryption key selection | this key | [1] | 2026-11-16 Sources: [1] Amazon Web Services. "kiro.dev/docs/enterprise/monitor-and-track/user-activity/opentelemetry/". https://kiro.dev/docs/enterprise/monitor-and-track/user-activity/opentelemetry/ Role: primary. Accessed: 2026-11-16T13:09:30Z Quote: "Create a symmetric customer managed AWS KMS key for encryption and decryption." (Supports: KMS key type) Quote: "The default aws/secretsmanager key can't be used because Kiro reads the secret from another AWS account." (Supports: Default key restriction) Quote: "The KMS key, Secrets Manager secret, and Kiro profile must be in the same AWS Region." (Supports: Region requirement) Quote: ""Service" : "q.amazonaws.com"" (Supports: Service principal) Quote: "You select this key as the encryption key when you create the secret." (Supports: Secret encryption key selection) Published: 2026-11-14T03:24:59Z Snapshot SHA-256: 615b7a24fc512d6a473867b7bb18b31e2e8980c678a37fd280c28de670c73443 (captured 2026-11-13T03:41:11Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:41:11Z, so the values verified then were kept. Cross-check: not-available at 2026-11-16T13:09:30Z. No independent second source is configured for this entry Last successful check: 2026-11-16T13:09:30Z Last attempt: 2026-11-20T13:26:59Z (failed) Notes and limitations: Extracted automatically from a single official source (section "Create a customer managed KMS key"). Related: https://latestn.com/tool/kiro/admin-and-enterprise/owner-lock-governance How do I enable the owner lock or configure governance policies like remote fleet policy in Kiro Crew? https://latestn.com/tool/kiro/admin-and-enterprise/pin-version-phased-rollout How do I pin a specific Kiro version or set up a phased rollout for managed updates? https://latestn.com/tool/kiro/admin-and-enterprise/prepare-s3-bucket-for-csv-reports How do I prepare an Amazon S3 bucket for Kiro CSV reports? https://latestn.com/tool/kiro/admin-and-enterprise/onboard-team-enterprise How do I onboard my team to Kiro Enterprise? https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-event-delivery How does Kiro send OpenTelemetry real-time events? https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-setup How do I create a KMS key to prepare credentials for OpenTelemetry in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:49:13Z | check-failed | Extraction did not pass verification: section "Create a customer managed KMS key" not found in the source (the page may have been reorganized) | — 2026-11-13T03:41:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup POST: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What KMS key and Secrets Manager secret do I need to configure for Kiro OpenTelemetry export? Revision 1, last verified 2026-11-16T13:09:30Z. https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup (accessed 2026-11-21T10:07:56Z). @misc{LatestN_tool_kiro_admin_and_enterprise_opentelemetry_kms_secret_setup_r1, title = {What KMS key and Secrets Manager secret do I need to configure for Kiro OpenTelemetry export?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup}}, note = {Revision 1; digest sha256:c9d1d34322e2ef6f; last verified 2026-11-16T13:09:30Z; accessed 2026-11-21T10:07:56Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup