Answer: To enable overages, sign in to the AWS Management Console, switch to the Kiro console, choose Settings, find the Kiro settings section, and turn on Overages. To set custom caps, open the Service Quotas console, search for Kiro, and find the quota named Maximum allowed overage per Kiro profile, or select the Manage link in the Overages setting; if you need a higher cap, request an increase through the same Service Quotas console. Status: Confirmed Entry: tool/kiro/pricing-and-limits/enable-overages-custom-caps Revision: 2 Digest: sha256:2e11c50b3992cc66 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:41:17Z Last changed: 2026-11-20T13:27:25Z (quota name: — → Maximum allowed overage per Kiro profile) Last verified: 2026-11-20T13:27:25Z Next check: 2026-11-21T13:27:25Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of default overage state | disabled | [1] | 2026-11-20 settings location | Settings | [1] | 2026-11-20 overage toggle | Overages | [1] | 2026-11-20 quota name | Maximum allowed overage per Kiro profile | [1] | 2026-11-20 Service Quotas region | us-east-1 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Manage subscriptions - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/subscription-management/ Role: primary. Accessed: 2026-11-20T13:27:25Z Quote: "By default, overages are disabled" (Supports: default overage state) Quote: "Choose Settings ." (Supports: settings location) Quote: "Turn on Overages ." (Supports: overage toggle) Quote: "Find the quota named Maximum allowed overage per Kiro profile" (Supports: quota name) Quote: "Open the Service Quotas console (opens in the us-east-1 region)." (Supports: Service Quotas region) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: cbcd7098f03095d160d4751cdefa751e310c8d7d535d4c17b295b27a6fcc6c0a (captured 2026-11-20T13:27:23Z) 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:25Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:27:25Z Last attempt: 2026-11-20T13:27:25Z Notes and limitations: Extracted automatically from a single official source (section "Enable overages for Kiro users"). Related: https://latestn.com/tool/kiro/pricing-and-limits/enterprise-tier-comparison What are the differences between Kiro enterprise billing tiers? https://latestn.com/tool/kiro/pricing-and-limits/file-explorer-limits What are the limits of Kiro's web file explorer? https://latestn.com/tool/kiro/pricing-and-limits/goal-limits-safeguards What are the limits and safeguards for goals in Kiro CLI? https://latestn.com/tool/kiro/pricing-and-limits/crew-resource-limits-machine-full How do I check Kiro Crew's resource limits and what happens when the machine is full? https://latestn.com/tool/kiro/pricing-and-limits/delivery-behavior-and-costs What are Kiro's OpenTelemetry event delivery behavior and costs? https://latestn.com/tool/kiro/pricing-and-limits/discord-message-rate-limits What are the message limits and rate limits for Kiro Crew on Discord? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:27:25Z | changed | quota name: — → Maximum allowed overage per Kiro profile | [1] 2026-11-20T13:27:25Z | changed | overage toggle: — → Overages | [1] 2026-11-20T13:27:25Z | changed | settings location: — → Settings | [1] 2026-11-20T13:27:25Z | changed | default overage state: — → disabled | [1] 2026-11-20T13:27:25Z | changed | cap quota name: Maximum allowed overage per Kiro profile → — | [1] 2026-11-20T13:27:25Z | changed | enable overages setting: Overages → — | [1] 2026-11-20T13:27:25Z | changed | overage default state: disabled → — | [1] 2026-11-13T03:41:17Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/pricing-and-limits/enable-overages-custom-caps/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/enable-overages-custom-caps POST: https://latestn.com/dispute/tool/kiro/pricing-and-limits/enable-overages-custom-caps with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/pricing-and-limits/enable-overages-custom-caps?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I enable overages for Kiro users and set custom caps? Revision 2, last verified 2026-11-20T13:27:25Z. https://latestn.com/tool/kiro/pricing-and-limits/enable-overages-custom-caps (accessed 2026-11-21T10:07:24Z). @misc{LatestN_tool_kiro_pricing_and_limits_enable_overages_custom_caps_r2, title = {How do I enable overages for Kiro users and set custom caps?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/pricing-and-limits/enable-overages-custom-caps}}, note = {Revision 2; digest sha256:2e11c50b3992cc66; last verified 2026-11-20T13:27:25Z; accessed 2026-11-21T10:07:24Z} } 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/enable-overages-custom-caps