I Tried Lowering the Overage Limit for Kiro (Enterprise Contract)
This page has been translated by machine translation. View original
Introduction
With the July 2026 update to Kiro under enterprise contracts, the cap on overage usage (overage) can now be managed through AWS Service Quotas.
The previous article tried raising the cap, but this article presents the results of lowering the cap through an AWS Support case.
What I Tested
The identifying information for the quota is as follows.
| Item | Value |
|---|---|
| ServiceCode | kiro |
| QuotaCode | L-75434B0B |
| QuotaName | Maximum allowed overage per Kiro profile |
| Unit | None (specify the dollar amount directly) |
| Adjustable | true |
| QuotaAppliedAtLevel | ACCOUNT |
This quota is the overage cap per subscription (user and group) within a Kiro profile.
Why Set the Cap at $200
The policy is to minimize the pay-as-you-go charge of $0.04 per credit that is incurred when the credits included with Kiro are exceeded. The desired value of $200 was decided on the assumption of operating with Pro Max ($100 per month / 5000 included credits). After using up the 5000 included credits, using an additional 5000 credits via overage comes to 5000 × $0.04 = $200. The overage unit price and the number of included credits for each plan are listed on Kiro's pricing page.
The assumed operation is to switch to Power before the overage for each subscription (user and group) reaches $200. This article does not verify the actual operation of switching to Power, nor the behavior of usage restrictions when the cap is reached. The basis for calculating the included-credit unit price of Pro Max (equivalent to $0.02/credit) and the break-even point for plan changes are summarized in the following article.
Specification That Does Not Allow Lowering via the API
Service Quotas' RequestServiceQuotaIncrease is an API that only accepts changes to a value larger than the current value, so it cannot be used for lowering.
If you submit a request specifying a value smaller than the current value, the following error is returned.
An error occurred (IllegalArgumentException) when calling the RequestServiceQuotaIncrease operation:
You must provide a quota value greater than the current quota value
Opening and Handling the AWS Support Case
When opening the case, I included the following information.
- AWS Account ID
- Service: Kiro
- Quota name: Maximum allowed overage per Kiro profile
- Quota code: L-75434B0B
- Region: us-east-1
- Current applied value: $420
- Desired value: $200
- Background explanation (the reason for wanting to set the overage cap to $200)
- The fact that lowering via the API was not possible, along with the error message
As background, I explained that $200 was set as the cap to be used as the criterion for deciding to switch to Power.
Here is an overview of the case.
| Item | Details |
|---|---|
| Subject | Request to decrease Kiro quota "Maximum allowed overage per Kiro profile" from $420 to $200 |
| Request | Lower L-75434B0B from $420 → $200 |
| Service category | service-service-quotas / general |
| Status | resolved |
The handling went as follows.
- 2026-07-13 06:56 UTC — Case opened
- 2026-07-16 07:13 UTC — Case resolved (status
resolved)
Checking the Quota Value After Lowering
After the case became resolved, I confirmed via the CLI that the quota value had been changed to $200.
aws service-quotas list-service-quotas \
--region us-east-1 \
--service-code kiro \
--query "Quotas[?QuotaCode=='L-75434B0B'].{QuotaName:QuotaName,Value:Value,Adjustable:Adjustable}"
[
{
"QuotaName": "Maximum allowed overage per Kiro profile",
"Value": 200.0,
"Adjustable": true
}
]
Summary
This time, I requested through an AWS Support case that the Kiro overage cap be lowered, and I was able to confirm the change to $200. In environments where Kiro is used via Kiro Web or headless, this can be set as a guardrail to keep down high pay-as-you-go charges caused by unintended long-running executions. If you manage an enterprise Kiro environment, I recommend checking the current setting value and configuring the overage cap to match your budget and usage policy.
