Amazon Redshift Service Level Agreement

Last Updated: May 19, 2022

This Amazon Redshift Service Level Agreement (“SLA”) is a policy governing the use of Amazon Redshift (“Amazon Redshift”) and applies separately to each account using Amazon Redshift. 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.
 
SLAs
 

AWS makes two SLA commitments for Redshift: (1) a Multi-Node Redshift SLA; and (2) a Single-Node Redshift SLA.

Multi-Node Redshift SLA

AWS will use commercially reasonable efforts to make each Multi-Node Cluster available with the Monthly Uptime Percentages set forth in the table below, during any monthly billing cycle (the “Multi-Node Redshift SLA”).

Monthly Uptime Percentage
 Service Credit Percentage
Less than 99.9% but equal to or greater than 99.0% 10%
Less than 99.0% but equal to or greater than 95.0% 25%
Less than 95% 100%

Single-Node Redshift SLA

For each individual Single-Node Cluster, AWS will use commercially reasonable efforts to make the Single-Node Cluster available with the Single-Node Uptime Percentages set forth in the table below, during any monthly billing cycle (the “Single-Node Redshift SLA”).

Single-Node 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% 25%
Less than 95% 100%

Service Credits are calculated as a percentage of the total charges paid by you for the Multi-Node Cluster or Single-Node Cluster, as applicable, in the affected AWS region for the monthly billing cycle in which the SLA, as applicable, was not met.

We will apply any Service Credits only against future Amazon Redshift payments otherwise due from you. At our discretion, we may issue the Service Credits 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. Service Credits 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. Unless otherwise provided in the Agreement, your sole and exclusive remedy for any unavailability or non-performance or other failure by us to provide Amazon Redshift is the receipt of Service Credits (if eligible) in accordance with the terms of this SLA.

Credit Request and Payment Procedures

To receive Service Credits, you will need to submit a claim by opening a case in the AWS Support Center. You may not combine or stack claims under the Multi-Node Redshift SLA and the Single-Node Redshift SLA for a particular Redshift deployment. Your 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 Multi-Node or Single-Node Redshift SLA, as applicable:

i. the words "Redshift SLA Credit Request" in the subject line;
ii. the dates and times of each Unavailability incident you are claiming;
iii. the database cluster names and the AWS regions of the affected cluster; and

iv. your request logs that document the errors and corroborate your claimed outage (any confidential or sensitive information in these logs should be removed or replaced with asterisks).
 
If a claim under the applicable SLA is confirmed by us, then we will issue the Service Credit to you within one billing cycle following the month in which the credit request occurred. Your failure to provide the credit requested and other information as required above will disqualify you from receiving Service Credits.
 
Amazon Redshift SLA Exclusions

The respective SLAs do not apply to any unavailability, suspension or termination of Amazon Redshift, or any other Amazon Redshift 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 Amazon Redshift; (ii) that result from any voluntary actions or inactions from you; (iii) that result from you not following the best practice operational recommendations described in the Amazon Redshift User Guide or the Amazon Redshift Advisor Recommendations; (iv) that result from your equipment, software or other technology; or (v) arising from our suspension and termination of your right to use Amazon Redshift in accordance with the Agreement.

If availability is impacted by factors other than those explicitly used in our Monthly Uptime Percentage or Single-Node Uptime Percentage calculation, as applicable, then we may issue a Service Credit considering such factors at our discretion.
 
Definitions
  • "Monthly Uptime Percentage" for a given Multi-Node Cluster is calculated by subtracting from 100% the percentage of 1 minute intervals during the monthly billing cycle in which the Multi-Node Cluster was "Unavailable". If you have been running that Multi-Node Cluster for only part of the month, your Multi-Node Cluster is assumed to be 100% available for the portion of the month that it was not running.
  • "Multi-Node Cluster” is defined as a cluster operating on a publicly available release version of Redshift that has two or more compute nodes and that is on the current or trailing maintenance track, as described in the Amazon Redshift User Guide.
  • A “Service Credit” is a dollar credit, calculated as set forth above, that we may credit back to an eligible, active AWS account.
  • "Single-Node Cluster" is defined as a cluster operating on a publicly available release version of Redshift that has no more than one compute node and that is on the current or trailing maintenance track, as described in the Amazon Redshift User Guide.
  • "Single-Node Uptime Percentage" for a given Single-Node Cluster is calculated by subtracting from 100% the percentage of 1 minute intervals during the monthly billing cycle in which the cluster was "Unavailable". If you have been running that Single-Node Cluster for only part of the month, your Single-Node Cluster is assumed to be 100% available for the portion of the month that it was not running.
  • "Unavailable" and “Unavailability” mean that all connections to a running cluster fail during a 1-minute interval.