Amazon Compute Service Level Agreement

Last Updated: August 24, 2021

This Amazon Compute Service Level Agreement (this “SLA”) is a policy governing the use of the Included Services (listed below) and applies separately to each account using the Included Services. In the event of a conflict between the terms of this SLA and the terms of the AWS Customer Agreement or other agreement with us governing your use of our Services (the “Agreement”), the terms and conditions of this SLA apply, but only to the extent of such conflict. Capitalized terms used herein but not defined herein shall have the meanings set forth in the Agreement.

Included Services

• Amazon Elastic Compute Cloud (Amazon EC2)*

• Amazon Elastic Block Store (Amazon EBS)

• Amazon Elastic Container Service (Amazon ECS)

• AWS Fargate for Amazon ECS and Amazon EKS

*For purposes of this SLA, Amazon EC2 includes any Amazon Elastic Graphics, Amazon Elastic Inference, and Elastic IP Address resources purchased with the relevant Amazon EC2 instance(s).

SLAs

AWS makes two SLA commitments for the Included Services: (1) a Region-Level SLA that governs Included Services deployed across multiple AZs or regions, and (2) an Instance-Level SLA that governs Amazon EC2 instances individually. 

Region-Level SLA

For Included Services with all running instances or tasks deployed concurrently across two or more AZs in the same region (or at least two regions if there’s only one AZ in a given region), AWS will use commercially reasonable efforts to make each Included Service 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”). In the event any of the Included Services do not meet the Region-Level SLA, you will be eligible to receive a Service Credit as described below.

Monthly Uptime Percentage

Service Credit Percentage

Less than 99.99% but equal to or greater than 99.0%

10%

Less than 99.0% but equal to or greater than 95.0%

30%

Less than 95.0%

100%

Instance-Level SLA

For each individual Amazon EC2 instance (“Single EC2 Instance”), AWS will use commercially reasonable efforts to make the Single EC2 Instance available with an Instance-Level Uptime Percentage of at least 99.5%, in each case during any monthly billing cycle (the “Instance-Level SLA”). In the event any Single EC2 Instance does not meet the Instance-Level SLA, you will be eligible to receive a Service Credit as described below.

Instance-Level Uptime Percentage

Service Credit Percentage

Less than 99.5% but equal to or greater than 99.0%

10%

Less than 99.0% but equal to or greater than 95.0%

30%

Less than 95.0%

100%

Note: In addition to the Instance-Level SLA, AWS will not charge you for any Single EC2 Instance that is Unavailable for more than six minutes of a clockhour. This applies automatically and you do not need to request credit for any such hour with more than six minutes of Unavailability.

SLA Credits

Service Credits are calculated as a percentage of the monthly bill (excluding one-time payments such as upfront payments made for Reserved Instances) for the individual Included Service in the affected AWS region that did not meet the Region-Level SLA, or for the Single EC2 Instance in the AWS region that did not meet the Instance-Level SLA, respectively.

We will apply any Service Credits only against future payments for the applicable Included Service otherwise due from you. At our discretion, we may issue the Service Credit to the credit card you used to pay for the billing cycle in which the Unavailability occurred. Service Credits will not entitle you to any refund or other payment from AWS. A Service Credit will be applicable and issued only if the credit amount for the applicable monthly billing cycle is greater than one dollar ($1 USD). Service Credits may not be transferred or applied to any other account.

Credit Request and Payment Procedures

To receive a Service Credit, you must submit a claim by opening a case in the AWS Support Center. You may only submit a claim under either the Region-Level SLA or the Instance-Level SLA, as these claims cannot be combined or stacked for a particular Single EC2 Instance. Your credit request must be received by us by the end of the second billing cycle after which the incident occurred and must include the information specified below for the Region-Level SLA and Instance-Level SLA, respectively.

Region-Level SLA requests must include:

  1. the words “Amazon Compute SLA Credit Request – Region-Level Claim” in the subject line;
  2. the dates, times, and affected AWS region of each Unavailability incident that you are claiming;
  3. the resource IDs for the affected Included Service; and
  4. your request logs that document the errors and corroborate your claimed outage**.

Instance-Level SLA requests must include: 

  1. the words “Amazon Compute SLA Credit Request – Instance-Level Claim” in the subject line;
  2. the dates, times, and the affected AWS region and AZ of each Unavailability incident that you are claiming;
  3. the resource IDs for the affected Single EC2 Instances; and
  4. your request logs and other data necessary for AWS to validate your claimed outage**.

** Please replace any confidential or sensitive information with asterisks.

If a claim under the Region-Level or Instance-Level SLA is confirmed by us as valid, we will issue you a Service Credit within one billing cycle following the month in which your request is confirmed by us.

Your failure to provide the requested and other information as required above will disqualify you from receiving a Service Credit. Unless otherwise provided in the Agreement, this SLA sets forth your sole and exclusive remedies, and AWS’ sole and exclusive obligations, for any unavailability, non-performance, or other failure by us to provide the Included Services.

Amazon Compute SLA Exclusions

The Region-Level SLA and Instance-Level SLA, respectively, do not apply to any unavailability, suspension or termination of an Included Service, or any other Included Service performance issues, directly or indirectly: (i) caused by factors outside of our reasonable control, including any force majeure event or Internet access or related problems beyond the demarcation point of the applicable Included Service; (ii) that result from any actions or inactions of you or any third party, including failure to acknowledge a recovery volume or respond to resource health concerns; (iii) that result from your equipment, software or other technology and/or third party equipment, software or other technology (other than third party equipment within our direct control); or (iv) arising from our suspension or termination of your right to use the applicable Included Service in accordance with the Agreement (collectively, the “Amazon Compute SLA Exclusions”). If availability is impacted by factors other than those used in our Monthly Uptime Percentage calculation, then we may issue a Service Credit considering such factors at our discretion.

SLA Definitions

  • “Availability Zone” and “AZ” mean an isolated location within an AWS region identified by a letter identifier following the AWS region code (e.g., us-west-1a).
  • “Monthly Uptime Percentage” is calculated by subtracting from 100% the percentage of minutes during the month in which any of the Included Services, as applicable, was in the state of Unavailability.
  • “Instance-Level Uptime Percentage” is calculated by subtracting from 100% the percentage of minutes during the month in which a Single EC2 Instance was in the state of Unavailability.
  • A “Service Credit” is a dollar credit, calculated as set forth above, that we may credit back to an eligible account.
  • “Unavailable” and “Unavailability” mean:
    • For the Instance-Level SLA, your Single EC2 Instance has no external connectivity.
    • For the Region-Level SLA applicable to Amazon EC2 (other than Single EC2 Instances), Amazon ECS, or AWS Fargate, when all of your running instances or running tasks, as applicable, deployed in two or more AZs in the same AWS region (or, if there is only one AZ in the AWS region, that AZ and an AZ in another AWS region) concurrently have no external connectivity.
    • For the Region-Level SLA applicable to Amazon EBS, when all of your attached volumes deployed in two or more AZs in the same AWS region (or, if there is only one AZ in the AWS region, that AZ and an AZ in another AWS region) perform zero read write IO, with pending IO in the queue.

Prior version(s)