# Service Quotas

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

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/service-quotas

> 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.

Practice exams covering Service Quotas: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 7 key features of Service Quotas

1. **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.
2. **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.
3. **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.
4. **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.
5. **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.
6. **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.
7. **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.

## Where Service Quotas is used

1. **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.
2. **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.
3. **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.
4. **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.
5. **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.

## How Service Quotas is priced

- **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.
- **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.

## Services Service Quotas works 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 CloudWatch](https://blowstack.com/tools/cloud-services-hub/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.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/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.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/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.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/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.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Service Quotas sends automatic quota management events to Amazon EventBridge. Rules can route these events to notification or remediation targets when quota utilization changes or a quota increase needs attention.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Service Quotas can use CloudWatch alarms with Amazon SNS notifications to alert you when usage approaches a supported quota. For example, an alarm can notify an operations email list when utilization crosses a configured threshold.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Service Quotas supports access through interface VPC endpoints, allowing workloads in a VPC to manage quotas without an internet gateway or NAT gateway.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: Service Quotas Automatic Management provides AWS Health notifications about quota utilization and automatic quota increase activity. These notifications help identify quotas that need attention and can be routed through Amazon EventBridge.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Service Quotas uses IAM policies to control who can view quotas, request increases, and manage organization-wide quota request templates. It also uses a service-linked role to access AWS Organizations when applying templates to new accounts.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Service Quotas integrates with AWS Organizations through quota increase request templates. An associated template automatically requests specified quota increases for new accounts created in the organization.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Service Quotas supports AWS PrivateLink interface endpoints for private access to its API. Requests can stay on the AWS network rather than traverse the public internet.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Service Quotas APIs are available through Step Functions AWS SDK integrations. A workflow can retrieve a quota, request an increase, and check the request status without a Lambda function making those calls.

## Service Quotas exam questions

Real practice exam questions on Service Quotas, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

A company deploys eight independent AWS CloudFormation stacks in parallel in us-east-1. Each stack creates 400 resources, and each template is within the per-template resource limit. Deployments succeed when the stacks are created individually, but the parallel rollout fails with an error indicating that the account has exceeded the number of resources allowed in concurrent stack operations.

A CloudOps engineer confirms that the applied concurrent-resources quota is 2,500 in us-east-1. No other stack operations are running, and the underlying services have sufficient quotas. The company requires enough quota for all 3,200 resources to be created concurrently in this account and Region.

Which solution meets this requirement?

**Correct answer:** Use Service Quotas to request a CloudFormation concurrent-resources quota of at least 3,200 in us-east-1, and verify that the applied quota has increased before retrying the parallel rollout.

**Explanation:** The failure is caused by the Regional quota for resources involved in concurrent CloudFormation stack operations. Requesting a sufficient total quota in the deployment Region and verifying its applied value addresses the constraint. Submitting a request alone does not mean the increase has taken effect.

### Question 2 (SAP-C03)

**Question:**

A company is preparing a stateless application for a scheduled sales event. The application runs on identical 8-vCPU EC2 instances distributed evenly across three Availability Zones in one AWS Region. Representative load tests show that each instance can sustain 600 requests per second while meeting the application's latency objective. Tests confirm that downstream services can support the planned load.

Peak demand is forecast to reach 18,000 requests per second. The company requires ready application capacity sufficient for 120% of forecast peak demand, even immediately after the complete loss of any one Availability Zone. Starting or resuming an instance and initializing the application takes 12 minutes. No additional instances can be counted toward the capacity requirement during that interval.

Other workloads continuously consume 160 vCPUs from the same Regional EC2 On-Demand vCPU quota. The applied quota is currently 576 vCPUs. All application instances count against this quota. Sufficient EC2 infrastructure capacity is available for the planned launches.

Which capacity plan meets all the requirements?

**Correct answer:** Obtain and verify an applied vCPU quota of at least 592. Before the event, launch and initialize 54 application instances, with 18 in each Availability Zone.

**Explanation:** The required surviving capacity is 18,000 × 1.20 = 21,600 requests per second, which requires 36 ready instances. With 18 instances in each of three Availability Zones, losing one zone leaves 36. The full application fleet consumes 54 × 8 = 432 vCPUs. Including the other workloads requires an applied quota of at least 432 + 160 = 592 vCPUs. Initializing all instances before the event avoids dependence on launches during the failure.

### Question 3 (DOP-C02)

**Question:**

A company deploys a production application by using a blue/green deployment pipeline in one AWS Region. The current environment has 40 On-Demand EC2 instances, and the replacement environment requires 60 instances. Each instance has 8 vCPUs. Both environments must remain running until validation finishes. Unrelated workloads in the same account and Region continuously use another 80 vCPUs from the same EC2 On-Demand quota category.

The applied quota for this category is 640 vCPUs. Previous deployments have failed when EC2 Auto Scaling could not launch replacement instances because this quota was exceeded. The Auto Scaling group maximum sizes and subnet capacity are sufficient. The company cannot stop existing workloads or change instance types.

Which change should a DevOps engineer make to the pipeline to prevent this quota-related deployment failure?

**Correct answer:** Use Service Quotas to request a total quota of 1,024 vCPUs for the applicable EC2 On-Demand category in the deployment account and Region. Gate deployment until the applied quota is confirmed to be at least 1,024 vCPUs.

**Explanation:** The overlapping environments and unrelated workloads require 880 vCPUs. A total quota of 1,024 vCPUs accommodates that peak. The request must target the correct quota category, account, and Region. Because quota increases can require review, the pipeline must verify the applied value before launching the replacement environment. This prevents the identified quota failure but does not guarantee EC2 capacity availability.

### Question 4 (SAA-C03)

**Question:**

A company runs an active-active application on AWS Lambda in two AWS Regions. Each Region normally receives 600 requests per second. If either Region fails, the surviving Region must handle all 1,200 requests per second. Each request invokes the same function once synchronously.

The function's average execution duration is 0.5 seconds during normal operation. Representative failure tests show that increased dependency latency raises the average execution duration to 1 second when one Region handles the entire workload. The company requires a Regional concurrency quota at least 25% above the calculated sustained failover concurrency requirement.

Each Region currently has an applied Lambda concurrent executions quota of 1,000. There are no other Lambda workloads or reserved concurrency settings in either Region. Traffic shifts gradually enough that Lambda's execution-environment scaling rate is not a constraint.

Which capacity plan meets the requirements?

**Correct answer:** Use Service Quotas to request a total concurrent executions quota of at least 1,500 in each Region. Verify that both increases are applied, and validate the configuration with representative failover load tests.

**Explanation:** The sustained failover requirement is 1,200 requests per second multiplied by 1 second, or 1,200 concurrent executions. Adding 25% headroom requires a quota of at least 1,500. Either Region might become the survivor, so both need the applied increase. Load testing validates the plan because a quota increase permits concurrency but does not itself provision capacity or prove application performance.

## Practice Service Quotas in a full exam

Questions on Service Quotas in each practice exam, with every answer option and an explanation for each:

- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 4 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 2 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 1 question
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 1 question

## What is Service Quotas

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.

Support can partially approve an increase request rather than granting the full requested value.

Service Quotas has nonadjustable limits on active increase requests: 20 per account globally, 2 per account per opt-in Region, and, within each Region, 1 per quota and 1 per resource.

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.

## Learn Service Quotas in lessons

4 short lessons on Service Quotas in 4 certification courses.

- SOA-C03: Service Quotas: quota increase workflow (Premium), https://app.blowstack.com/lessons/service-quotas-quota-increase-workflow-soa-c03
- SAP-C03: Service Quotas: automated quota headroom management (Premium), https://app.blowstack.com/lessons/service-quotas-automated-quota-headroom-management-sap-c03
- DOP-C02: Service Quotas: managing quota headroom (Premium), https://app.blowstack.com/lessons/service-quotas-managing-quota-headroom-dop-c02
- SAA-C03: Service Quotas: managing quota headroom (Premium), https://app.blowstack.com/lessons/service-quotas-managing-quota-headroom-saa-c03

## Concepts related to Service Quotas

- [Capacity Planning](https://blowstack.com/tools/cloud-concepts-hub/capacity-planning): Capacity planning is the process of estimating workload demand and arranging sufficient resources to meet performance, growth, and resilience requirements within cost constraints.
