Answer: Open the AWS KMS console in the Region of your Kiro profile, choose Customer managed keys, then Create key, selecting Symmetric key type and Encrypt and decrypt key usage, then add a key policy statement allowing Kiro to decrypt via Secrets Manager. Status: Confirmed Entry: tool/kiro/admin-and-enterprise/opentelemetry-kms-key-setup Revision: 2 Digest: sha256:c1a6f1350cb759d3 (changes whenever the content changes) Timeline: Created: 2026-11-17T13:49:15Z Last changed: 2026-11-20T13:27:01Z (actions: — → kms:Decrypt) Last verified: 2026-11-20T13:27:01Z Next check: 2026-11-21T13:27:01Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of key type | Symmetric | [1] | 2026-11-20 key usage | Encrypt and decrypt | [1] | 2026-11-20 alias example | kiro-otel-export | [1] | 2026-11-20 policy Sid | AllowKiroDecryptViaSecretsManager | [1] | 2026-11-20 service principal | q.amazonaws.com | [1] | 2026-11-20 actions | kms:Decrypt | [1] | 2026-11-20 via service condition | secretsmanager..amazonaws.com | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Prepare credentials - Monitor per-user activity - Monitor and track - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/monitor-and-track/user-activity/prepare-credentials/ Role: primary. Accessed: 2026-11-20T13:27:01Z Quote: "For Key type , choose Symmetric ." (Supports: key type) Quote: "For Key usage , choose Encrypt and decrypt ." (Supports: key usage) Quote: "Enter an Alias , such as kiro-otel-export ." (Supports: alias example) Quote: ""Sid" : "AllowKiroDecryptViaSecretsManager"" (Supports: policy Sid) Quote: ""Service" : "q.amazonaws.com"" (Supports: service principal) Quote: ""Action" : [ "kms:Decrypt" , "kms:DescribeKey" ]" (Supports: actions) Quote: ""kms:ViaService" : "secretsmanager..amazonaws.com"" (Supports: via service condition) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: d67a29838f74014c0a9195336099188713e41b527b6f42226d3373cda705d421 (captured 2026-11-20T13:27:02Z) 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]. Cross-check: not-available at 2026-11-20T13:27:01Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:27:01Z Last attempt: 2026-11-20T13:27:01Z Notes and limitations: Extracted automatically from a single official source (section "Step 1: Create a KMS key"). Related: https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-secret-setup What KMS key and Secrets Manager secret do I need to configure for Kiro OpenTelemetry export? 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/okta-scim-provisioning How do I configure SCIM provisioning and group synchronization for Kiro in Okta? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:27:01Z | changed | actions: — → kms:Decrypt | [1] 2026-11-20T13:27:01Z | changed | service principal: — → q.amazonaws.com | [1] 2026-11-20T13:27:01Z | changed | policy actions: kms:Decrypt → — | [1] 2026-11-20T13:27:01Z | changed | policy service principal: q.amazonaws.com → — | [1] 2026-11-17T13:49:15Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-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-key-setup POST: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-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-key-setup?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I create a KMS key to prepare credentials for OpenTelemetry in Kiro? Revision 2, last verified 2026-11-20T13:27:01Z. https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-setup (accessed 2026-11-21T10:06:20Z). @misc{LatestN_tool_kiro_admin_and_enterprise_opentelemetry_kms_key_setup_r2, title = {How do I create a KMS key to prepare credentials for OpenTelemetry in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/admin-and-enterprise/opentelemetry-kms-key-setup}}, note = {Revision 2; digest sha256:c1a6f1350cb759d3; last verified 2026-11-20T13:27:01Z; accessed 2026-11-21T10:06:20Z} } 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-key-setup