aws-limits

Name: aws-limits
Availability: InStock
Author: WalletConnect

Scan infrastructure code for AWS service quota violations.

14|Updated Jan 8, 2026

Search Tags:#aws #cloudformation #limits #terraform #infrastructure-as-code #cdk #quotas

Ready to run

npx skills add https://github.com/WalletConnect/skills --skill aws-limits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aws-limits
Source: https://github.com/WalletConnect/skills/tree/main/skills/aws-limits
Command: npx skills add https://github.com/WalletConnect/skills --skill aws-limits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews AWS service quota occurrences in infrastructure code before deployment to production, helping teams avoid outages caused by limits.

Core Features & Use Cases

Identify AWS services in IaC (Terraform, CloudFormation, CDK, Pulumi, or SDKs) and map them to known quotas.
Validate against high-risk hard limits and soft defaults from REFERENCE.md, surfacing violations with severity and remediation notes.
Provide links to official AWS documentation and recommended mitigations to guide architecture decisions and change planning.
Use cases include pre-commit checks on IaC, PR review guidance for changes that affect quotas, and runbooks for remediation when limits are approached.

Quick Start

Run the AWS limits review against your infrastructure codebase to surface quota violations and suggested mitigations.

Frequently Asked Questions about aws-limits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check AWS service quotas in Terraform or CloudFormation before deployment?▼

You can identify AWS service quota violations in infrastructure code by scanning Terraform, CloudFormation, CDK, or Pulumi configurations. The skill validates provisioning patterns against known hard limits and soft defaults, surfacing risks with severity and remediation notes before production.

What AWS services have hard limits that can cause deployment failures in infrastructure as code?▼

AWS services including Lambda, API Gateway, S3, DynamoDB, and Step Functions have hard limits and soft defaults that can cause deployment failures. Scanning infrastructure code validates provisioning patterns against these quotas, flagging violations and suggesting mitigations to prevent outages.

Does this quota scanning approach work with CDK and Pulumi, or only Terraform and CloudFormation?▼

This quota scanning approach works with CDK and Pulumi in addition to Terraform and CloudFormation. It also supports SDK-based provisioning, validating infrastructure code across all these frameworks to identify AWS service quota violations and suggest appropriate mitigations.

How do I add AWS quota checks to my pull request review process?▼

To add AWS quota checks to your pull request review process, run the limits review against infrastructure codebase changes. This surfaces quota violations with links to official AWS documentation and recommended mitigations, providing PR review guidance for changes that affect service limits.

What is the difference between AWS hard limits and soft defaults when scanning infrastructure code?▼

AWS hard limits are enforced service quotas that cannot be exceeded without a quota increase, while soft defaults are configurable limits that may be approached. Scanning infrastructure code validates against both, prioritizing risks based on expected scale and providing remediation guidance.

Why do AWS quota violations cause outages and how can I prevent them in IaC?▼

AWS quota violations cause outages when infrastructure code attempts to provision resources beyond service limits. Prevent these issues by scanning IaC files before deployment to identify services exceeding quotas, using context about expected scale to prioritize risks and suggest architectural mitigations.