Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

service-quota-check

Use this skill during any incident investigation, capacity planning, or

yuriypr · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add aws/tools-for-devops-agent --skill service-quota-check

About this skill


name: service-quota-check description: Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits. Activate when you observe throttling errors (ThrottlingException, TooManyRequestsException, LimitExceededException), resource creation failures, capacity-related alarms, or when a recommendation involves provisioning new AWS resources. metadata: author: yuriypr version: "1.0.0" aws-devops-agent-skills.agent-types: "Chat tasks, Incident RCA" aws-devops-agent-skills.aws-services: "AWS Service Quotas, Amazon CloudWatch" aws-devops-agent-skills.technical-domains: "Operations, Capacity Planning"

Service Quota Check

Use this skill to check AWS service quota utilization during investigations and before provisioning new resources. It determines whether a quota is nearing its limit (85%+ utilization) and takes action: requesting a quota increase via the Service Quotas API when possible, or recommending a support case when programmatic increases are not supported.

When to Use This Skill

  • An error message indicates throttling or limit exceeded (e.g., ThrottlingException, TooManyRequestsException, LimitExceededException, ResourceLimitExceeded).
  • A resource creation or scaling operation fails with capacity errors.
  • An investigation recommendation involves provisioning additional AWS resources (e.g., adding EC2 instances, creating VPCs, adding NAT Gateways, launching RDS instances).
  • Capacity planning or pre-launch readiness checks.
  • Proactive monitoring of quota utilization across services.

Prerequisites

  • The agent must have permissions to call Service Quotas APIs:
    • servicequotas:ListServices
    • servicequotas:ListServiceQuotas
    • servicequotas:GetServiceQuota
    • servicequotas:RequestServiceQuotaIncrease
    • servicequotas:ListRequestedServiceQuotaChangeHistory
    • servicequotas:CreateSupportCase
  • For utilization data via CloudWatch, the agent needs:
    • cloudwatch:GetMetricData
    • cloudwatch:GetMetricStatistics
  • Service Quotas is a regional service. Quotas must be checked in the region where resources are deployed.

Step 1: Identify the Service and Quota Context

Determine which service and quota to check based on the investigation context:

  1. From error messages — extract the service name and specific limit mentioned.
  2. From recommendations — if the recommendation is to provision resources, identify the service (e.g., EC2, VPC, RDS, Lambda, ELB) and the resource type.
  3. From alarms — if a CloudWatch alarm indicates capacity pressure, identify the underlying service.

Common service codes

AWS ServiceService Code
Amazon EC2ec2
Amazon VPCvpc
Elastic Load Balancingelasticloadbalancing
Amazon RDSrds
AWS Lambdalambda
Amazon ECSecs
Amazon EKSeks
Amazon S3s3
Amazon DynamoDBdynamodb
AWS Fargatefargate
Amazon CloudWatchmonitoring
AWS CloudFormationcloudformation
Amazon SQSsqs
Amazon SNSsns
Amazon ElastiCacheelasticache
Amazon OpenSearch Servicees
Auto Scalingautoscaling

If you do not know the service code, use:

aws service-quotas list-services \
  --query "Services[?contains(ServiceName, '<keyword>')]" \
  --region <region>

Step 2: Retrieve Quota Value and Utilization

Get the applied quota value

aws service-quotas get-service-quota \
  --service-code <service-code> \
  --quota-code <quota-code> \
  --region <region>

The response includes:

  • Value — the current quota limit (applied value, or default if no increase was granted)
  • Adjustable — whether the quota can be increased
  • UsageMetric — CloudWatch metric to check current utilization (if available)

If you do not know the quota code

List all quotas for the service:

aws service-quotas list-service-quotas \
  --service-code <service-code> \
  --region <region>

Filter by quota name keyword:

aws service-quotas list-service-quotas \
  --service-code <service-code> \
  --region <region> \
  --query "Quotas[?contains(QuotaName, '<keyword>')]"

Get current utilization via CloudWatch

If the UsageMetric field is present in the quota response, query CloudWatch for actual usage:

aws cloudwatch get-metric-statistics \
  --namespace "<MetricNamespace>" \
  --metric-name "<MetricName>" \
  --dimensions <MetricDimensions> \
  --start-time "<15-minutes-ago-ISO8601>" \
  --end-time "<now-ISO8601>" \
  --period 300 \
  --statistics <MetricStatisticRecommendation> \
  --region <region>

The UsageMetric object from the quota response provides all the parameters:

  • MetricNamespace — typically AWS/Usage
  • MetricName — typically ResourceCount
  • MetricDimensions — service-specific dimensions (e.g., Class, Resource, Service, Type)
  • MetricStatisticRecommendation — either Maximum or Sum

Alternative: count resources directly

If no UsageMetric is available, count resources using the service's Describe/List APIs:

ServiceCommand to count resources
EC2 instancesaws ec2 describe-instances --query "Reservations[].Instances[] | length(@)"
VPCsaws ec2 describe-vpcs --query "Vpcs | length(@)"
NAT Gatewaysaws ec2 describe-nat-gateways --filter Name=state,Values=available --query "NatGateways | length(@)"
EIPsaws ec2 describe-addresses --query "Addresses | length(@)"
RDS instancesaws rds describe-db-instances --query "DBInstances | length(@)"
Lambda functionsaws lambda list-functions --query "Functions | length(@)"
ECS servicesaws ecs list-services --cluster <cluster> --query "serviceArns | length(@)"
ALBs`aws elbv2 describe-load-balancers --que
Read the complete source ↗