CLOUD SERVICE · AWS

Service Quotas - Service Quotas is an AWS service for viewing supported service quotas, checking applied limits, and requesting quota increases.

Service Quotas provides a central console and API for managing supported resource and operation limits across AWS services. Engineers use it to inspect default and applied quota values, track increase requests, and configure utilization alarms for quotas with compatible CloudWatch metrics.

Cloud Services Hub →

What is Service Quotas

Read the extensive description

AWS services enforce quotas on resources, throughput, and operations. Service Quotas provides a central place to discover supported quotas, inspect their values, and request increases when adjustment is supported. Examples include Amazon EC2 On-Demand vCPU quotas and AWS Lambda concurrent execution quotas. A quota defines an allowed limit; it does not reserve infrastructure capacity or provision resources.

Begin by selecting the account and AWS Region where the workload runs. Distinguish the AWS default quota value from the applied value for that account. An approved increase can make the applied value different from the default. Many quotas are Regional, while others are global or apply to particular resources. Inspect the quota's scope and context rather than assuming that an increase affects every Region or resource.

The console, AWS CLI, and AWS SDKs provide access to quota discovery and management operations. Automation uses service codes and quota codes to identify quotas consistently. Retrieve the applied value and adjustment eligibility before submitting a request. When requesting an increase, specify the desired total quota value rather than the amount to add to the existing value.

Increase requests can require review and are not guaranteed to be approved. Track request status and any associated support case, then verify the applied value before allowing a dependent deployment to proceed. Submit requests before planned growth because processing is not necessarily immediate. A higher EC2 quota, for example, does not guarantee that a chosen instance type is available in a particular Availability Zone.

Not every AWS limit appears in Service Quotas, and not every listed quota can be increased through it. Some limits are fixed; others require a service-specific workflow or an AWS Support request. Consult the owning service's documentation when a quota is absent, its applied value is unavailable, or its adjustment path is unclear.

For quotas with compatible CloudWatch usage metrics, configure utilization alarms that leave enough time to investigate growth or request additional headroom. Metric availability is quota-specific. Combine alarms with application and service telemetry to distinguish quota exhaustion from capacity shortages, request throttling, and configuration errors.

In multi-account environments, implement onboarding checks that retrieve quotas in each target account and Region. Custom automation can assume an IAM role in each account, compare applied values with workload requirements, and submit supported increase requests when authorized. Keep approval verification separate from request submission. Apply least-privilege permissions and use CloudTrail to audit management activity.

Key Service Quotas Features

Centralized quota discovery

Find supported AWS services and quotas through a common console or API. Check each quota's scope because limits can apply to an account, a Region, or a particular resource.

Default and applied values

Inspect AWS default values separately from the values applied to your account. Use applied values for deployment checks instead of assuming the documented default is the current limit.

Quota increase requests

Request higher values for supported adjustable quotas. Specify the desired total value and allow time for review before the workload needs the additional headroom.

Request status and history

Inspect increase requests and their processing status. Confirm that the applied quota has changed rather than treating successful request submission as approval.

CLI and SDK automation

Use service codes and quota codes to retrieve values and submit supported requests programmatically. Handle API throttling, missing applied values, and asynchronous request processing in automation.

CloudWatch utilization alarms

Monitor utilization and configure alarms for quotas with compatible CloudWatch usage metrics. Verify metric availability and dimensions for each quota before relying on an alarm.

IAM-controlled access

Grant quota inspection separately from permissions to request increases. Limit automation to the required actions and use resource-level permissions where supported.

Service Quotas Use Cases

Deployment readiness checks

Compare current consumption plus planned growth with the relevant applied quotas before deployment. For an EC2 expansion, check the Regional vCPU quota for the instance purchasing option and instance category being used.

Peak traffic preparation

Review quota utilization ahead of seasonal traffic, launches, or migrations. Request increases early and verify the resulting applied values before the event.

Account onboarding

Run a custom onboarding workflow that checks required quotas in each new account and target Region. Submit supported increases through authorized API calls and track them until the required values are applied.

Regional expansion

Inventory quotas in a destination Region before replicating a workload. Request Regional increases where necessary instead of assuming approvals from another Region carry over.

Quota-related incident investigation

Compare service errors and usage telemetry with applied quota values to identify exhausted limits. Separately investigate infrastructure capacity, throttling behavior, and configuration errors that can produce similar symptoms.

Service Quotas pricing models

Associated service usage

CloudWatch alarms and automation components can incur their standard charges. Resources consumed after a quota increase are billed under the pricing of the owning AWS service.

No additional service charge

Service Quotas is available at no additional charge. Viewing supported quotas and requesting increases does not itself provision resources or create resource usage charges.

Services Service Quotas integrates with

A common operational pattern combines Service Quotas with CloudWatch to detect approaching limits before they affect deployments or traffic. For quotas with compatible usage metrics, configure alarms with sufficient headroom for investigation and request processing. Use service telemetry alongside these alarms because not every quota has utilization metrics, and not every capacity error indicates quota exhaustion.Custom Lambda automation can retrieve applied values and compare them with workload requirements. In a multi-account environment, the function can assume narrowly scoped IAM roles in target accounts and perform checks in each required Region. Separate read-only inventory from permission to submit increases, and track request completion independently from API submission.For an EC2 rollout, a readiness check can compare existing and planned vCPU consumption with the relevant quota before scaling begins. Verify the applied value after approval and retain separate checks for actual instance availability. CloudTrail provides an audit record of Service Quotas API activity, helping teams investigate who requested changes and when.

Amazon EC2

Service Quotas exposes supported EC2 quotas and their increase workflows. For example, check the applicable Regional On-Demand vCPU quota before increasing an Auto Scaling group's desired capacity. A quota increase does not reserve instances or guarantee capacity in a chosen Availability Zone.

Open Amazon EC2 →

AWS CloudTrail

CloudTrail records Service Quotas API activity for auditing and investigation. For example, identify the principal that submitted a quota increase request and when the request occurred. Configure a trail or event data store for retention and analysis beyond event history.

Open AWS CloudTrail →

Amazon CloudWatch

Service Quotas uses compatible CloudWatch usage metrics to support quota utilization monitoring and alarms. For example, configure an alarm for a supported quota when utilization reaches a threshold that leaves time to request an increase. Not every quota exposes the required metric, so validate monitoring support individually.

Open Amazon CloudWatch →

AWS Lambda

Lambda functions can call Service Quotas APIs through AWS SDKs to perform custom inventory and readiness checks. For example, an onboarding function can compare an account's applied quotas with workload requirements and submit supported increase requests. The workflow must separately track request completion and verify the applied values.

Open AWS Lambda →