Lesson 038 · AWS Learning Path

AWS 038: Service quotas and AWS Support plans

Anil Jalela · Published Aug 2, 2025 · 5 min read

The problem

A launch fails during an event because the team assumed account capacity was unlimited. A support case is opened with the wrong severity and without evidence. The architecture had resources, but no quota or support readiness.

Quotas and support plans solve different problems.

Final outcome

You will inspect one regional and one global quota, calculate headroom, create a quota-readiness record, and select an appropriate current AWS Support plan for three business scenarios.

Quota terms

Not every service quota appears in Service Quotas. Not every quota is adjustable. Approval is not immediate or guaranteed.

Quotas are not capacity reservations

An approved quota increase raises an account limit. It does not guarantee that a specific instance type or service capacity will be available in a particular Availability Zone at launch time.

Similarly, a low quota does not control cost. A workload can incur substantial cost below a quota, and some expensive dimensions use different limits.

Read-only Console exercise

1. Run the AWS 033 preflight.
2. Open Service Quotas.
3. Confirm the fixed course Region.
4. Choose AWS services, then Amazon Elastic Compute Cloud (Amazon EC2).
5. Find a quota relevant to On-Demand instance capacity.
6. Record AWS default value, applied value, adjustability, usage visibility, and Region.
7. Choose a global service such as IAM and inspect one documented quota.
8. Open Request history without submitting a request.

Quota names and values change. Record the exact current name and timestamp rather than copying a static value from this lesson.

Read-only CLI exercise

List EC2 quota metadata:

aws service-quotas list-service-quotas \
  --profile course \
  --region ap-south-1 \
  --service-code ec2 \
  --max-items 20 \
  --query '{Quotas:Quotas[].{Name:QuotaName,Value:Value,Adjustable:Adjustable,Global:GlobalQuota},NextToken:NextToken}' \
  --output json \
  --no-cli-pager

Because --max-items 20 limits the result, this is a sample and not a complete inventory. The query retains the continuation token when one is present.

For a known quota code discovered in the Console:

aws service-quotas get-service-quota \
  --profile course \
  --region ap-south-1 \
  --service-code ec2 \
  --quota-code <quota-code> \
  --output json \
  --no-cli-pager

Replace the placeholder. Do not include angle brackets literally.

If access is denied, document the required read action. Do not request broad administrator permission.

Headroom

For a quota value of 100 and current usage of 65:

headroom = quota - usage = 35
utilization = usage / quota * 100 = 65%

Set operational thresholds before emergency. A request can take time, and a large request may need business justification.

Create quota-readiness.md:

Add planned event demand and show whether current headroom is sufficient.

Safe increase process

This lesson does not submit a request. The production process is:

1. prove account and Region;
2. verify exact quota and current applied value;
3. measure usage and forecast;
4. calculate the requested value;
5. include business and event justification;
6. request early;
7. track status;
8. retest provisioning;
9. monitor utilization.

Requesting the maximum imaginable value without evidence can delay review and weakens governance.

Current AWS Support plan model

AWS Support offerings changed. As of the technical review date, the principal documented plans are:

• Basic Support;
• AWS Business Support+;
• AWS Enterprise Support;
• AWS Unified Operations.

AWS documentation also announces end-of-support timing for older Developer, Business, and Enterprise On-Ramp plans. Do not use an old certification table as a current purchasing guide. Verify the live plan page before a decision.

Plan distinctions

Basic Support includes account and billing assistance, service quota increase assistance, documentation, forums, service health information, and selected checks. It does not provide the same technical case access and response commitments as paid production plans.

Business Support+ adds around-the-clock access to Cloud Support Engineers, business-critical response targets, broader Trusted Advisor capabilities, and support APIs according to the current offering.

Enterprise Support adds a designated Technical Account Manager, faster production-critical engagement target, strategic reviews, event support capabilities, and current security-incident benefits.

Unified Operations targets broader critical operations needs with its current defined service model. Features, minimum charges, and eligibility must be verified from AWS pricing and plan documentation.

Support decision scenarios

1. Personal learning account with no production workload: Basic is normally appropriate. Use course troubleshooting and account/billing support boundaries.
2. Revenue-generating application requiring 24/7 technical case access and a business-critical response target: evaluate Business Support+.
3. Enterprise portfolio with production-critical systems, named technical guidance, strategic reviews, and major event planning: evaluate Enterprise or Unified Operations according to current requirements.

Support does not replace internal monitoring, incident command, backups, runbooks, testing, or architecture.

Prepare a useful support case

Include:

• account and Region through secure case context;
• affected service and redacted resource IDs;
• UTC start time and current impact;
• exact error and request ID;
• reproduction steps;
• expected and actual behavior;
• recent changes;
• evidence already checked;
• safe contact path;
• severity justified by business impact.

Do not paste passwords, secret keys, session tokens, or unnecessary customer data.

Common failures

Completion gate

Pass when the learner records one regional and one global quota, calculates headroom, explains adjustability and lead time, does not submit an unnecessary increase, and selects current support plans for all three scenarios with cost and response reasoning.

No quota or support-plan change was performed.

Official sources

• Service Quotas introduction
• Request a quota increase
• AWS Support plans
• AWS Support plan comparison