Amazon RDS Service Level Agreement

 Last Updated: March 2, 2022

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

Service Commitment

AWS will use commercially reasonable efforts to make Multi-AZ instances and Multi-AZ DB clusters available with a Monthly Uptime Percentage of at least 99.95% during any monthly billing cycle (the "Service Commitment"). In the event Amazon RDS does not meet the Service Commitment, you will be eligible to receive a Service Credit as described below.

Service Credits

Service Credits are calculated as a percentage of the charges paid by you for the Multi-AZ instances or Multi-AZ DB clusters that did not meet the Monthly Uptime Percentage commitment in a billing cycle in accordance with the schedule below.

Monthly Uptime Percentage

Service Credit Percentage

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


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


Less than 95.0%


We will apply any Service Credits only against future Amazon RDS payments 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. 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 RDS is the receipt of a Service Credit (if eligible) in accordance with the terms of this SLA.

Credit Request and Payment Procedures

To receive a Service Credit, you will need to submit a claim by opening a case in the AWS Support Center. To be eligible, the credit request must be received by us by the end of the second billing cycle after which the incident occurred and must include:

i. the words "SLA Credit Request" in the subject line;
ii. the dates and times of each Unavailability incident you are claiming;
iii. the DB Instance IDs and the AWS regions of the affected Multi-AZ instances or Multi-AZ DB clusters; 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 the Monthly Uptime Percentage of such request is confirmed by us and is less than the Service Commitment, then we will issue the Service Credit to you within one billing cycle following the month in which the request occurred. Your failure to provide the request and other information as required above will disqualify you from receiving a Service Credit.

Amazon RDS SLA Exclusions

The Service Commitment does not apply to any unavailability, suspension or termination of Amazon RDS, or any other Amazon RDS performance issues: (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 RDS; (ii) that result from any voluntary actions or inactions from you or any third party; (iii) that result from instances belonging to the Micro DB instance class or other instance classes which have similar CPU and memory resource limitations; (iv) that result from you not following the basic operational guidelines described in the Amazon RDS User Guide (e.g., overloading a database instance to the point it is inoperable, creating excessively large number of tables that significantly increase the recovery time etc.); (v) caused by underlying database engine software that lead to repeated database crashes or an inoperable database instance; (vi) that result in long recovery time due to insufficient IO capacity for your database workload; (vii) 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); (viii) that result from any maintenance as provided for pursuant to the AWS Agreement; or (ix) arising from our suspension and termination of your right to use Amazon RDS in accordance with the Agreement (collectively, the "Amazon RDS SLA Exclusions").

If availability is impacted by factors other than those explicitly used in our Monthly Uptime Percentage calculation, then we may issue a Service Credit considering such factors at our discretion.


  • "Monthly Uptime Percentage" for a given Multi-AZ instance or Multi-AZ DB cluster is calculated by subtracting from 100% the percentage of 1 minute intervals during the monthly billing cycle in which the Multi-AZ instance or Multi-AZ DB cluster was "Unavailable". If you have been running that Multi-AZ instance or Multi-AZ DB cluster for only part of the month, your Multi-AZ instance or Multi-AZ DB cluster is assumed to be 100% available for the portion of the month that it was not running. Monthly Uptime Percentage measurements exclude downtime resulting directly or indirectly from any Amazon RDS SLA Exclusion.
  • "Multi-AZ DB instance" means an Amazon RDS for MySQL, MariaDB, Oracle, PostgreSQL, or SQL Server database instance with the Multi-AZ DB Instance deployment option selected.
  • "Multi-AZ DB Cluster" means an Amazon RDS for MySQL or PostgreSQL database cluster with the Multi-AZ DB Cluster deployment option selected.
  • A "Service Credit" is a dollar credit, calculated as set forth above, that we may credit back to an eligible account.
  • "Unavailable" means that all connection requests to the running Multi-AZ instance or Multi-AZ DB cluster fail during a 1 minute interval.

Prior Version(s)