# Agent Cloud Quotas and Service Limits
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

Cloud quotas and service limits are first-class evidence when an agent sees provisioning failures, throttling, or capacity errors that are not caused by application code.

## Core Explanation

Agents often need to distinguish broken code from exhausted platform limits. Instance counts, IP addresses, GPU capacity, API calls, load balancers, disks, and regional resources can all fail because the account, project, subscription, or region hit a quota.

The safe workflow is to identify the provider, service, region, quota name, current usage, configured limit, recent increase requests, and whether the failure is a rate limit or a resource capacity limit.

## Source-Mapped Facts

- AWS documentation describes Service Quotas as a service for viewing and managing quotas for AWS services. ([source](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html))
- Google Cloud documentation describes quotas as limits that restrict how much of a Google Cloud resource a project or organization can use. ([source](https://cloud.google.com/docs/quotas))
- Microsoft Azure documentation describes quotas as limits on resources, services, and subscriptions. ([source](https://learn.microsoft.com/en-us/azure/quotas/quotas-overview))

## Further Reading

- [AWS Service Quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html)
- [Google Cloud Quotas](https://cloud.google.com/docs/quotas)
- [Azure Quotas Overview](https://learn.microsoft.com/en-us/azure/quotas/quotas-overview)