Answer: The default finite TTL is 72h, and it requires the reaper stack (install-reaper.sh), an in-account Lambda that removes expired deployments; without it, finite-TTL deploys are refused (409). The reaper only ever touches resources that carry the kirocrew:site + kirocrew:managed tags and match the managed naming scheme, and cannot delete anything else in your account. Status: Confirmed Entry: tool/kiro/features/ttl-and-reaper Revision: 1 Digest: sha256:3e8055af62169632 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:38:34Z Last changed: 2026-11-13T03:38:34Z Last verified: 2026-11-20T13:23:11Z Next check: 2026-11-21T13:23:11Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Default TTL | 72h | hours | [1] | 2026-11-20 Reaper requirement | install-reaper.sh | | [1] | 2026-11-20 Reaper function | an in-account Lambda that removes expired deployments | | [1] | 2026-11-20 Without reaper | 409 | | [1] | 2026-11-20 Persistent TTL | ttl_hours: 0 | | [1] | 2026-11-20 Reaper scope tags | kirocrew:site + kirocrew:managed | | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Artifacts - Features - Crew - Docs - Kiro". https://kiro.dev/docs/crew/features/artifact-deploy/ Role: primary. Accessed: 2026-11-20T13:23:11Z Quote: "Finite TTL (default 72h)" (Supports: Default TTL) Quote: "Requires the reaper stack ( install-reaper.sh )" (Supports: Reaper requirement) Quote: "an in-account Lambda that removes expired deployments" (Supports: Reaper function) Quote: "Without it, finite-TTL deploys are refused (409)." (Supports: Without reaper) Quote: "Persistent ( ttl_hours: 0 ) No reaper required." (Supports: Persistent TTL) Quote: "The reaper only ever touches resources that carry the kirocrew:site + kirocrew:managed tags and match the managed naming scheme." (Supports: Reaper scope tags) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: c358b9a26182fb0edca93f964dffe5895c4b3c1e0a85ac2cd040a0120618db55 (captured 2026-11-20T13:23:12Z) 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:23:11Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:23:11Z Last attempt: 2026-11-20T13:23:11Z Notes and limitations: Extracted automatically from a single official source (section "TTL and the reaper"). Related: https://latestn.com/tool/kiro/features/upload-existing-designs How do I upload an existing design when creating a Kiro feature spec? https://latestn.com/tool/kiro/features/use-checkpoints-and-rewind How do I use checkpoints and rewind in Kiro? https://latestn.com/tool/kiro/features/use-specs-for-complex-work How do I use specifications in Kiro for complex work? https://latestn.com/tool/kiro/features/three-phase-workflow What is the three-phase workflow for Kiro specs? https://latestn.com/tool/kiro/features/tool-search-availability Which Kiro versions or plans support MCP Tool Search? https://latestn.com/tool/kiro/features/transcription-backends What transcription backends does Kiro CLI voice mode support? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:38:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/ttl-and-reaper/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/features/ttl-and-reaper POST: https://latestn.com/dispute/tool/kiro/features/ttl-and-reaper with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/ttl-and-reaper?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What is the TTL and how does the reaper work for Kiro Crew deployed artifacts? Revision 1, last verified 2026-11-20T13:23:11Z. https://latestn.com/tool/kiro/features/ttl-and-reaper (accessed 2026-11-21T10:03:55Z). @misc{LatestN_tool_kiro_features_ttl_and_reaper_r1, title = {What is the TTL and how does the reaper work for Kiro Crew deployed artifacts?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/ttl-and-reaper}}, note = {Revision 1; digest sha256:3e8055af62169632; last verified 2026-11-20T13:23:11Z; accessed 2026-11-21T10:03:55Z} } 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/features/ttl-and-reaper