I tried lowering the overage limit for Kiro (Enterprise contract)
This page has been translated by machine translation. View original
Introduction
Kiro for enterprise contracts received an update in July 2026 that allows managing the overage cap through AWS Service Quotas.
While the previous article attempted to raise the limit, this article presents the results of lowering the limit through an AWS Support case.
What Was Tested
The quota identification information is as follows.
| Item | Value |
|---|---|
| ServiceCode | kiro |
| QuotaCode | L-75434B0B |
| QuotaName | Maximum allowed overage per Kiro profile |
| Unit | None (dollar amount specified directly) |
| Adjustable | true |
| QuotaAppliedAtLevel | ACCOUNT |
This quota is the overage cap per subscription (user and group) within a Kiro profile.
Why Set a $200 Cap
The policy is to minimize the pay-as-you-go charges of $0.04 per credit that occur when exceeding Kiro's included credits. The desired value of $200 was determined based on operating under the Pro Max plan ($100/month, 5,000 included credits). After exhausting the 5,000 included credits, using an additional 5,000 credits via overage results in 5,000 × $0.04 = $200. The overage unit price and the number of included credits per plan are listed on the Kiro pricing page.
The intended operation is to switch to Power before overage reaches $200 for each subscription (user and group). This article does not verify the actual steps for switching to Power or the behavior of usage restrictions when the cap is reached. The basis for calculating the included credit unit price for Pro Max (equivalent to $0.02/credit) and the break-even point for plan changes are summarized in the following article.
Specification: Cannot Be Lowered via API
Service Quotas' RequestServiceQuotaIncrease is an API that only accepts changes to values greater than the current value and cannot be used to lower it.
When 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
Filing and Response of the AWS Support Case
When filing the case, the following information was included.
- 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 (reason for wanting to set the overage cap to $200)
- The fact that the reduction could not be done via API and the error message
As background context, I communicated that $200 was being set as the threshold to use when deciding to switch to Power.
Here is a summary 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 Classification | service-service-quotas / general |
| Status | resolved |
The response proceeded as follows.
- 2026-07-13 06:56 UTC — Case filed
- 2026-07-16 07:13 UTC — Case resolved (status
resolved)
Verifying the Quota Value After Reduction
After the case was marked resolved, the CLI was used to confirm 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, we requested a reduction of the Kiro overage cap through an AWS Support case and confirmed the change to $200. In environments using Kiro Web or headless Kiro, this can be set as a guardrail to prevent unexpectedly high pay-as-you-go charges from unintended long-running executions. If you manage an enterprise Kiro environment, we recommend checking your current settings and configuring the overage cap to align with your budget and usage policies.
