Overview — Cloud Quota & Limits Reference

A machine-readable reference of default service quotas and hard limits for AWS,

GCP, and Azure — the numbers agents and engineers routinely guess wrong. "How many

Lambda concurrent executions by default? What's the max SQS message size? RDS

connection cap? VPCs per region?" This ships those as structured JSON you can load,

diff, and check against, plus a guide on which limits are soft (raise via support)

vs hard (architect around).

Cloud providers change quotas over time and many are account/region specific.

This is a reference baseline (documented defaults at time of authoring) to

plan against — always confirm the live value in your account's quota console

before a production decision. Each entry notes soft vs hard.

Why this is worth buying vs asking a model

LLMs confidently hallucinate specific numbers ("Lambda allows 10,000 concurrent

by default" — it's 1,000 unburstable default in many regions). Being wrong here

causes real outages and failed capacity plans. This is curated, structured, and

labelled soft/hard so you can trust and automate against it.

What's inside

• data/aws-limits.json — common EC2/Lambda/S3/SQS/RDS/DynamoDB/API-GW/VPC limits.
• data/gcp-limits.json — Compute/Cloud Run/Cloud SQL/Pub-Sub/GCS limits.
• data/azure-limits.json — VM/Functions/Storage/Service-Bus/SQL limits.
• SOFT-VS-HARD.md — which to plan around vs request an increase for, and how.
• data/schema.json — the JSON shape, so you can validate/extend it.

Use it

# e.g. check your planned concurrency against the default
python3 -c "import json; d=json.load(open('data/aws-limits.json')); \
print(d['lambda']['concurrent_executions'])"

Each entry: { value, unit, scope, soft|hard, note }.

Requirements

None. JSON — load from any language.