Answer: Kiro Crew LTS requires a Kiro profile created in US East (N. Virginia) with Enterprise Management on; support for existing profiles and for profiles in Europe comes later. Rules for web_search and web_fetch are decided by the Kiro service on every client, not by Crew, and Crew's own fetch tool is governed by network_egress. Status: Confirmed Entry: tool/kiro/pricing-and-limits/lts-limits Revision: 2 Digest: sha256:cf0988e3e49abf66 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:30Z Last changed: 2026-11-20T13:24:26Z (Crew fetch tool governance: — → network_egress) Last verified: 2026-11-20T13:24:26Z Next check: 2026-11-21T13:24:26Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Profile region requirement | US East (N. Virginia) | [1] | 2026-11-20 Enterprise Management requirement | Enterprise Management on | [1] | 2026-11-20 Existing profiles and Europe support | comes later | [1] | 2026-11-20 web_search and web_fetch rule decider | the Kiro service on every client | [1] | 2026-11-20 Crew fetch tool governance | network_egress | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Kiro Crew LTS - Crew - Docs - Kiro". https://kiro.dev/docs/crew/lts/ Role: primary. Accessed: 2026-11-20T13:24:26Z Quote: "Kiro Crew LTS needs a Kiro profile created in US East (N. Virginia) with Enterprise Management on." (Supports: Profile region requirement) Quote: "with Enterprise Management on" (Supports: Enterprise Management requirement) Quote: "Support for existing profiles and for profiles in Europe comes later." (Supports: Existing profiles and Europe support) Quote: "Rules for web_search and web_fetch are decided by the Kiro service on every client, not by Crew" (Supports: web_search and web_fetch rule decider) Quote: "Crew's own fetch tool is governed by network_egress" (Supports: Crew fetch tool governance) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 1bf874ef12770e8584e9c8f53ff316129ce3a8ab6c3d3fd029a617962866fcd6 (captured 2026-11-20T13:24:24Z) 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:24:26Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:26Z Last attempt: 2026-11-20T13:24:26Z Notes and limitations: Extracted automatically from a single official source (section "Limits"). Related: https://latestn.com/tool/kiro/pricing-and-limits/monthly-limit-reached What happens when I reach the monthly limit of my Kiro plan? https://latestn.com/tool/kiro/pricing-and-limits/opentelemetry-export-limits What are the limits and behavior of Kiro's OpenTelemetry export? https://latestn.com/tool/kiro/pricing-and-limits/private-connectivity-limits What are the behavior and limits of Kiro private connectivity? https://latestn.com/tool/kiro/pricing-and-limits/how-additional-credits-work How do additional credits work in Kiro Enterprise credit pooling? https://latestn.com/tool/kiro/pricing-and-limits/kiro-mobile-availability Where is Kiro Mobile available? https://latestn.com/tool/kiro/pricing-and-limits/low-resource-notifications What are low resource notifications in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:26Z | changed | Crew fetch tool governance: — → network_egress | [1] 2026-11-20T13:24:26Z | changed | web_search and web_fetch rule decider: — → the Kiro service on every client | [1] 2026-11-20T13:24:26Z | changed | Enterprise Management requirement: — → Enterprise Management on | [1] 2026-11-20T13:24:26Z | changed | Profile region requirement: — → US East (N. Virginia) | [1] 2026-11-20T13:24:26Z | changed | Enterprise Management: Enterprise Management on → — | [1] 2026-11-20T13:24:26Z | changed | Region requirement: US East (N. Virginia) → — | [1] 2026-11-13T03:39:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/pricing-and-limits/lts-limits/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/pricing-and-limits/lts-limits POST: https://latestn.com/dispute/tool/kiro/pricing-and-limits/lts-limits with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/pricing-and-limits/lts-limits?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What limits apply to Kiro Crew LTS? Revision 2, last verified 2026-11-20T13:24:26Z. https://latestn.com/tool/kiro/pricing-and-limits/lts-limits (accessed 2026-11-21T10:02:32Z). @misc{LatestN_tool_kiro_pricing_and_limits_lts_limits_r2, title = {What limits apply to Kiro Crew LTS?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/pricing-and-limits/lts-limits}}, note = {Revision 2; digest sha256:cf0988e3e49abf66; last verified 2026-11-20T13:24:26Z; accessed 2026-11-21T10:02:32Z} } 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/pricing-and-limits/lts-limits