AWS Lambda SLAAWS · Compute · AWS · Compute
Promise vs reality
Downtime used against the allowance
3 d of major incidents, 16.4x the allowance4.4 h allowed in 365 days
3 major and 0 minor incidents; worst region me-central-1. 0 min degraded (not counted).
Major incident minutes per month
Allowed per month: 22 min
- Promised
- 99.95%
- Observed, 365d
- 99.178%
- Major incident time
- 3 d
- Credit on first breach
- 10%
Commitments and credits
- StandardAll Lambda functions per AWS region99.95%
Monthly uptime below, credit of the bill
- Below 99.95%10%
- Below 99%25%
- Below 95%100%
Terms
- Measured
- Average of 5-minute Availability (share of requests not failing with 500/503) per AWS region
- Credit cap
- Up to 100% of Lambda charges in the affected region at the lowest tier; applied against future Lambda payments; issued only if over $1
- Claim window
- By the end of the second billing cycle after which the incident occurred
- How to claim
- Open a case in the AWS Support Center with 'SLA Credit Request' in the subject line and request logs
Not covered
- Factors outside AWS's reasonable control
- Voluntary customer actions (e.g. custom 500/503 codes, misconfigured VPC/security groups, disabled encryption keys)
- Not following Lambda User Guide best practices
- Customer equipment, software or other technology
- AWS suspension or termination of the right to use Lambda
AWS will use commercially reasonable efforts to make Lambda available with a Monthly Uptime Percentage for each AWS region, during any monthly billing cycle, of at least 99.95% (the “Service Commitment”).
Custom 500/503 status codes emitted by the customer's function code are not counted as Errors.
Evidence: incidents, last 365 days
Other compute SLAs
ServiceDowntime vs allowed
Amazon EC2AWS99.99% / 99.178%
Cloudflare WorkersCloudflare99.99% / 100%
Confluent Cloud for Apache FlinkConfluent99.99% / 99.628%
Droplets (CPU)DigitalOcean99.99% / 100%
Compute EngineGoogle Cloud99.99% / 99.927%
Azure FunctionsMicrosoft Azure99.95% / n/a
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.