Standard AWS SLAs give you credits worth a fraction of your downtime losses. Enterprise customers with EDP agreements can negotiate meaningful uptime commitments, enhanced credit structures, and tighter exclusion definitions — but only if they know what to ask for.
As part of our cloud enterprise negotiation series, understanding AWS SLA structure is foundational before attempting any negotiation. AWS publishes individual Service Level Agreements for each of its 200+ services. These are not centralised in a single document — each service has its own SLA page, and commitments vary significantly across the portfolio.
For core compute infrastructure, the headline numbers look reasonable. EC2 and EBS in multi-AZ configurations commit to 99.99% monthly uptime — approximately 4.4 minutes of allowable downtime per month. Amazon S3 commits to 99.9%, while RDS Multi-AZ sits at 99.95%. However, several critical caveats apply that most customers only discover during an incident.
| AWS Service | Standard SLA | Allowable Downtime/Month | Max Credit |
|---|---|---|---|
| EC2 Multi-AZ | 99.99% | 4.4 minutes | 30% of monthly charges |
| EC2 Single-AZ | 99.5% | 3.65 hours | 10% of monthly charges |
| Amazon S3 | 99.9% | 43.8 minutes | 25% of monthly charges |
| RDS Multi-AZ | 99.95% | 21.9 minutes | 25% of monthly charges |
| RDS Single-AZ | 99.5% | 3.65 hours | 10% of monthly charges |
| Lambda | 99.95% | 21.9 minutes | 25% of monthly charges |
| EKS | 99.95% | 21.9 minutes | 25% of monthly charges |
| AWS Direct Connect | 99.9% | 43.8 minutes | 10% of monthly charges |
The fundamental problem with AWS standard SLAs is the disconnect between credit value and business impact. Consider a financial services firm running $500,000/month in AWS charges that experiences an 8-hour EC2 outage. Under standard SLA terms, they might receive a credit of $150,000 (30% of monthly charges). But the business impact — lost transactions, regulatory exposure, remediation costs, and reputational damage — could easily exceed $5 million.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
AWS SLA credits are calculated as a percentage of your monthly bill for the affected service — not as compensation for your actual business losses. For mission-critical workloads, the maximum credit is rarely proportionate to real downtime costs. This makes contractual SLA negotiation essential for enterprises with critical AWS dependencies.
Beyond the credit cap problem, the standard SLA has three additional weaknesses that enterprise negotiators target. First, the definition of "downtime" is narrow — AWS measures availability at the service endpoint, not at your application layer. Your application can be unavailable due to an AWS issue while the service technically shows as "available." Second, the credit claim process requires customers to submit requests within 30 days and provide sufficient evidence, creating an administrative burden during the worst possible time. Third, single-AZ deployments receive dramatically worse SLAs, creating a perverse incentive that AWS doesn't always make explicit during sales.
When you reach EDP negotiation stage, the following metrics should be on your SLA agenda. Not all will be achievable — AWS has commercial limits on what it will offer — but pushing on multiple fronts increases the probability of meaningful improvements in the areas that matter most to your business.
Standard multi-AZ EC2 at 99.99% is already high, but for critical services like RDS or Direct Connect, pushing from 99.9% to 99.95% or 99.99% reduces allowable downtime from 43 minutes to 4–21 minutes per month. For payment processing or real-time trading systems, this matters significantly.
Standard AWS SLAs measure availability at the AWS service level. Negotiate for application-level measurement — if your application is down because of AWS, that counts regardless of whether the underlying AWS service shows as technically available. This is a significant concession and typically requires strong commercial relationship leverage.
Standard credits cap at 10–30% of monthly charges for the affected service. Enterprise customers with EDP agreements sometimes negotiate credits up to 100% of monthly charges for critical service outages, particularly for extended (multi-hour) incidents. A tiered credit structure — higher percentages for longer outages — is a common negotiated outcome.
AWS Enterprise Support (included in EDP agreements above certain thresholds) provides 15-minute response for critical issues. Negotiate the definition of "critical" to align with your operational reality, and seek contractual commitments on escalation paths to senior AWS engineering, not just support tier escalations.
Standard AWS SLA credits are applied as statement credits to your next bill — they don't reduce your current invoice, can't be converted to cash, and expire if you leave AWS. For large EDP customers, negotiating the credit structure itself is often as valuable as improving the uptime commitment.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
| Credit Structure | Standard AWS | Negotiated Enterprise |
|---|---|---|
| Credit form | Statement credit | Statement credit or invoice reduction |
| Credit cap (service outage) | 10–30% of monthly charges | Up to 100% for extended outages |
| Credit claim window | 30 days from incident | 90 days or automatic processing |
| Credit transferability | Not transferable | Sometimes transferable within org |
| Multi-service outage credits | Per-service caps apply separately | Aggregate cap negotiable |
| Consequential damages | Excluded entirely | Not typically available |
AWS will not agree to consequential damages clauses — this is a firm commercial policy. The negotiation ceiling for financial remedies is enhanced credits, improved credit caps, and streamlined claims processes. Organisations requiring true business interruption coverage for AWS outages should maintain appropriate cyber and business continuity insurance alongside contractual SLA protections.
AWS standard SLA exclusions are broad and can significantly erode the practical value of published commitments. Understanding and negotiating exclusions is often more impactful than chasing small improvements in headline uptime percentages.
Force majeure exclusions are standard and largely non-negotiable, but the definition can be tightened. Ensure the clause is limited to genuinely unforeseeable events — not infrastructure capacity issues that AWS should have anticipated.
Customer-caused failures are the most significant exclusion in practice. If your misconfiguration caused a cascade, AWS may deny the credit even if AWS infrastructure amplified the impact. Negotiate clear delineation of where AWS responsibility ends and customer responsibility begins, ideally with AWS providing rapid determination in disputed cases.
Scheduled maintenance exclusions are standard. Push for advance notice commitments (currently 5–7 days for planned maintenance), maintenance windows that align with your low-traffic periods, and notification channels beyond email (Slack/PagerDuty integration for critical maintenance).
Single-AZ exclusions are the most commercially impactful. Standard SLAs explicitly exclude or dramatically reduce coverage for single-AZ deployments. Many enterprises run dev/test workloads in single-AZ for cost reasons — ensure your SLA negotiations clarify exactly which workloads require multi-AZ protection and which are intentionally accepting lower availability guarantees.
AWS Enterprise Discount Program (EDP) agreements — typically available to customers committing $1M+ annually — are the primary vehicle for SLA customisation. EDP negotiations typically focus on pricing discounts (covered in our cloud enterprise discount guide), but SLA improvements should always be on the agenda.
AWS Enterprise Support, included or discounted within EDP arrangements, provides its own SLA framework: 15-minute response for business-critical issues, dedicated Technical Account Manager (TAM) access, and Infrastructure Event Management for major launches. Negotiating the contractual commitments around TAM engagement, proactive reviews, and architecture guidance is as important as the headline response time SLAs.
For customers running AWS GovCloud or AWS for regulated industries (financial services, healthcare, defence), additional SLA considerations apply around data residency, audit log availability, and compliance-related uptime requirements. These verticals often have more negotiation latitude because AWS's market penetration in heavily regulated sectors depends on meeting enterprise procurement standards that commercial SLA terms don't satisfy.
Our analysis of top AWS negotiation firms shows that the most effective advisors treat SLA negotiation as part of an integrated commercial strategy — not as a separate legal exercise. Combining EDP discount negotiation with SLA improvement, credits optimisation, and marketplace spend alignment creates the strongest possible position.
Negotiating AWS SLAs for enterprise workloads?
Our vetted advisors have structured EDP agreements and SLA improvements for enterprise customers spending $1M–$50M+ annually on AWS.