Amazon EC2 SLAAWS · Compute · AWS · Compute
Promise vs reality
Downtime used against the allowance
3 major and 0 minor incidents; worst region me-central-1. 0 min degraded (not counted).
Major incident minutes per month
Allowed per month: 4.4 min
- Promised
- 99.99%
- Observed, 365d
- 99.178%
- Major incident time
- 3 d
- Credit on first breach
- 10%
Commitments and credits
- Region-LevelAll running instances deployed concurrently across two or more AZs in the same region (or two regions if the region has one AZ)99.99%
Monthly uptime below, credit of the bill
- Below 99.99%10%
- Below 99%30%
- Below 95%100%
- Instance-LevelEach individual EC2 instance (Single EC2 Instance)99.5%
Monthly uptime below, credit of the bill
- Below 99.5%10%
- Below 99%30%
- Below 95%100%
Terms
- Measured
- Region-Level: Monthly Uptime Percentage per AWS region (minutes all multi-AZ instances concurrently lack external connectivity). Instance-Level: per single instance per month.
- Credit cap
- Up to 100% of the monthly bill for EC2 in the affected region (or for the affected instance) at the lowest tier; credits apply only against future EC2 payments and are 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 subject 'Amazon Compute SLA Credit Request - Region-Level Claim' or '- Instance-Level Claim', plus resource IDs and request logs
Not covered
- Factors outside AWS's reasonable control, including force majeure and Internet problems beyond the EC2 demarcation point
- Customer actions or inactions, including failure to acknowledge a recovery volume or respond to resource health concerns
- Customer equipment, software or other technology
- AWS suspension or termination of the customer's right to use EC2
AWS will use commercially reasonable efforts to make Amazon EC2 available for each AWS region with a Monthly Uptime Percentage of at least 99.99%, in each case during any monthly billing cycle (the “Region-Level SLA”).
Region-Level and Instance-Level claims cannot be combined or stacked for the same instance. Separately, AWS automatically does not charge for a Single EC2 Instance unavailable for more than six minutes of a clock hour. Since May 25, 2022 this SLA covers EC2 only (EBS, ECS and Fargate were previously in the same Compute SLA).
Evidence: incidents, last 365 days
SLA changes
- May25Amazon EC2Amazon Compute SLA narrowed to EC2 only; the May 5, 2022 version listed EC2, EBS, ECS and Fargate as Included Services under one SLA. Percentages unchanged (99.99% region, 99.5% instance).Source
- May5Amazon EC2Instance-Level SLA of 99.5% monthly with 10/30/100% credits introduced, replacing the July 22, 2020 'Hourly Commitment' (Single EC2 Instance Hourly Uptime Percentage of at least 90% per clock hour, otherwise that instance hour is not charged).Source
- Mar19Amazon EC2Third credit tier added: below 95.0% now earns a 100% credit (February 12, 2018 version topped out at 30% for 'Less than 99.0%').Source
- Nov15Amazon EC2Region-level EC2 (and EBS) commitment raised from 99.95% to 99.99%. June 1, 2013 version: 'Monthly Uptime Percentage ... of at least 99.95%'; November 15, 2017 version: 'of at least 99.99%'. Credit tiers stayed 10% / 30%.Source
Other compute SLAs
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%
AWS LambdaAWS99.95% / 99.178%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean99.95% / 100%
Azure FunctionsMicrosoft Azure99.95% / n/a
Confluent Cloud ksqlDBConfluent99.9% / 99.628%
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.