AWS EC2 SLA Credits & Refunds

EC2 outages cost engineering teams twice: once in lost productivity, and again in unclaimed service credits sitting on the table because nobody filed a ticket in time. Here's how the EC2 SLA actually works, what AWS will and won't credit you for, and how teams are automating the claim process end-to-end.

What this guide covers

• The official AWS EC2 uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file an EC2 credit request inside the AWS claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about AWS EC2 SLAs

What is the typical SLA uptime guarantee for AWS EC2?

The Amazon Compute SLA commits to a 99.99% Region-Level Monthly Uptime Percentage when you deploy instances across multiple Availability Zones, and a separate 99.5% Instance-Level commitment for individual instances. Service credits scale at 10%, 25%, and 100% as uptime falls below the applicable tier.

How do I claim AWS EC2 SLA credits after an outage?

Open a billing case in the AWS Support Center within 60 days of the affected billing period (the exact window is in the EC2 SLA itself). The case needs: the affected resource IDs, timestamps of the disruption in UTC, your monitoring evidence (CloudWatch metrics, error logs, or third-party uptime monitoring) cross-referenced against the AWS Health Dashboard, and your calculation of the Monthly Uptime Percentage. AWS reviews the case manually and applies any granted credit to your next invoice rather than refunding cash. Teams that file these regularly automate the evidence-gathering step because it's the most error-prone — a claim missing the wrong field gets denied and has to be refiled.

What exclusions apply to the AWS EC2 SLA?

For EC2, the Region-Level 99.99% commitment only applies if your workload runs across two or more Availability Zones in the affected region — a single-AZ outage that takes down a non-redundant deployment qualifies only under the lower 99.5% Instance-Level tier.

Why is it difficult to get refunds for EC2 outages manually?

Compute outages rarely show up cleanly. An EC2 workload might be partially degraded — some instances fail, others stay healthy — and the SLA only counts the portion of capacity that was actually unavailable. To prove a claim you need per-instance (or per-task) error-rate data, not just an aggregate dashboard. Most teams discover this only when their first credit request comes back denied for "insufficient evidence."

Related AWS SLA guides

Other AWS services that share the same claim window and Support Center workflow:

• AWS Lambda SLA credits — Compute
• AWS EKS SLA credits — Compute
• AWS ECS SLA credits — Compute
• AWS S3 SLA credits — Storage

Stop leaving AWS credits unclaimed

The hardest part of recovering EC2 credits isn't the SLA — it's the lag between an outage and the moment somebody on your team has the bandwidth to file the case. By the time the FinOps team gets around to it, the evidence has rolled out of CloudWatch and the billing window is closing.

Next Signal watches AWS Health and your own observability data, detects EC2 SLA breaches in real time, assembles the evidence package the way AWS expects it, and files the billing case for you. See how it works or start a free trial.