Cost and price for AWS API Gateway vary by API type (HTTP vs REST vs WebSocket), traffic, and features such as caching and data transfer. This article outlines typical price ranges in USD, with clear low–average–high estimates to help budget planning.
Assumptions: US region, standard usage, no reserved capacity, and no enterprise discounts unless noted.
| Item | Low | Average | High | Notes |
|---|---|---|---|---|
| Invocations (API calls) | $0.90 per 1M calls | $1.20 per 1M calls | $1.60 per 1M calls | Prices differ by API type (HTTP vs REST vs WebSocket). |
| Data transfer out to the internet | $0.04 per GB | $0.09 per GB | $0.12 per GB | Tiered pricing applies; initial free data transfer may apply in some accounts. |
| Caching (REST API cache) | $0.02 per hour per cache unit | $0.04 per hour per cache unit | $0.08 per hour per cache unit | Optional feature; reduces downstream invocation costs. |
| Custom domain names | $0.00–$1.50 per month | $0.50 per month | $1.50 per month | Depends on certificate management and routing requirements. |
| Edge-optimized vs Regional | Included in base pricing | Included in base pricing | Difference mainly in data transfer patterns | Edge vs regional affects latency-related costs. |
Overview Of Costs
Cloud API costs for API Gateway hinge on usage volume, API type, and ancillary features like caching and data transfer. For budgeting, most projects revolve around three levers: number of invocations, data transferred out, and optional caching. This section provides total project ranges and per-unit ranges with brief assumptions to help forecast monthly bills.
Assumptions: US East region, standard REST or HTTP APIs, no private integrations, no custom authorizers beyond basic AWS IAM/JWT validation.
Cost Breakdown
Detailed costs by category help translate usage into dollars. The following table presents a breakdown that combines totals with per-unit pricing where relevant.
| Category | Assumed Usage | Materials | Labor | Permits | Delivery/Disposal |
|---|---|---|---|---|---|
| Invocations | 1–10M/month | $0.90–$1.60 per 1M calls | — | — | — |
| Data transfer out | 10–100 GB/month | $0.04–$0.12/GB | — | — | — |
| Caching | 1–5 cache units | $0.02–$0.08/hour per unit | — | — | — |
| Custom domains | 1 domain | $0–$1.50/month | — | — | — |
| Totals (monthly) | — | $0.90–$1.60 per 1M calls + data transfer + caching | — | — | — |
Formula note: data-formula=”monthly_invocations × price_per_million”> + data_transfer_cost + caching_cost + domain_cost.
Factors That Affect Price
Price drivers for API Gateway fall into API type, traffic shape, and feature choices. Major variables include API type (HTTP vs REST vs WebSocket), peak and sustained invocation rate, data transfer volumes, and whether caching or custom authorizers are enabled. Higher concurrency and larger payloads raise per-unit costs, while caching can lower downstream invocation charges.
Assumptions: typical production workloads with bursts during business hours and moderate payload sizes.
Ways To Save
Cost optimization for API Gateway often focuses on reducing data transfer and leveraging caching. Consider using HTTP APIs for lower per-call pricing where compatible, enable caching with sensible TTLs, and consolidate endpoints to reduce total invocations. Monitoring usage patterns helps identify over-provisioned cache or idle domains.
Assumptions: standard monitoring setup, no reserved capacity.
Regional Price Differences
Prices can vary by U.S. region due to data transfer routes and regional pricing tiers. The following compares three representative markets and highlights typical deltas in costs, not including promotions or committed-use discounts.
- East Coast (us-east-1) vs West Coast (us-west-2): regional differences often amount to +/- 5–15% in data transfer and request pricing depending on traffic patterns.
- Urban centers vs Rural areas: higher outbound data costs in dense urban regions due to backbone routing may push costs by 5–10% on data transfer.
- Midwest regional hubs: generally align with national averages within a +/-5% band.
Assumptions: standard AWS public pricing, no interconnect discounts.
Real-World Pricing Examples
Three scenario cards illustrate how costs can scale with usage and feature choices. Each card specifies specs, labor hours (if applicable), per-unit pricing, and totals. Scenarios assume HTTP API usage with optional caching and a single custom domain.
Basic
Specs: 2 endpoints, 2M invocations/month, 20 GB data out, no caching.
Estimated: Invocations $1.20/1M, Data $0.09/GB, Totals ≈ $2.40 + $1.80 = $4.20/month.
Mid-Range
Specs: 6 endpoints, 10M invocations/month, 100 GB data out, 1 cache unit (24 hours).
Estimated: Invocations $1.20/1M, Data $0.09/GB, Caching $0.04/hour, Domain $0.50/month, Totals ≈ $12 + $9 + $24 + $0.50 ≈ $45.50/month.
Premium
Specs: 15 endpoints, 50M invocations/month, 1 TB data out, 5 cache units, 3 custom domains.
Estimated: Invocations $1.60/1M, Data $0.12/GB, Caching $0.08/hour, Domains $1.50/month each, Totals ≈ $80 + $120 + $96 + $4.50 ≈ $300.50/month.
Assumptions: region us-east-1, HTTP API, standard authentication, no WAF or private integrations.