Amazon Aurora Service Level Agreement for Amazon Web Services (Ningxia Region)

This Amazon Aurora Service Level Agreement for Amazon Web Services (Ningxia Region) (“SLA”) is a policy governing the use of Amazon Aurora under the terms of the Western Cloud Data Customer Agreement for Amazon Web Services (Ningxia Region) (available at https://www.amazonaws.cn/agreement/ningxia and as updated from time to time, collectively with other agreement with us governing your use of our Services, the “Agreement”) between Ningxia Western Cloud Data Technology Co. Ltd. (“Western Cloud Data”, “us” or “we”) and you. This SLA applies separately to each account using Amazon Aurora. In the event of a conflict between the terms of this SLA and the terms of 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

We will use commercially reasonable efforts to make Multi-AZ Clusters available with a Monthly Uptime Percentage of at least 99.99% during any monthly billing cycle (the “Service Commitment”). In the event Amazon Aurora does not meet the Service Commitment, you will be eligible to receive a Service Credit as described below. The Service Commitment and Service Credits provided to you under this SLA will be provided to you only in connection with your use of Amazon Aurora from Amazon Web Services China (Ningxia) region. This SLA does not authorize you to receive any Service Commitment or Service Credits from any other Amazon Web Services regions.

Service Credits

Service Credits are calculated as a percentage of the charges paid by you for the Multi-AZ Clusters that did not meet the Service Commitment in a billing cycle in accordance with the schedule below.

We will apply any Service Credits only against future Amazon Aurora payments otherwise due from you. At our discretion, we may issue the Service Credit to the bank 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 us. A Service Credit will be applicable and issued only if the credit amount for the applicable monthly billing cycle is greater than one Renminbi (¥1 Renminbi). 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 Aurora is the receipt of a Service Credit (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 Amazon Web Services 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:

1. the words “SLA Credit Request” in the subject line;
2. the dates and times of each Unavailability incident you are claiming;
3. the DB cluster IDs and the affected Multi-AZ Clusters; and
4. 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 Aurora SLA Exclusions

The Service Commitment does not apply to any unavailability, suspension or termination of Amazon Aurora, or any other Amazon Aurora 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 Aurora; (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 Aurora User Guide (e.g., overloading a database instance to the point it is inoperable, creating an excessively large number of tables that significantly increases the recovery time, etc.); (v) caused by underlying database engine software that leads 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 Agreement; or (ix) arising from our suspension or termination of your right to use Amazon Aurora in accordance with the Agreement (collectively, the “Amazon Aurora 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.

Definitions

• “Monthly Uptime Percentage” for a given Multi-AZ Cluster is calculated by subtracting from 100% the percentage of 1minute intervals during the monthly billing cycle in which the Multi-AZ Cluster was Unavailable. If you have been running that Multi-AZ Cluster for only part of the month, your Multi-AZ 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 Aurora SLA Exclusions.
• “Multi-AZ Cluster” means an Amazon Aurora cluster (for either the MySQL-compatible edition or the PostgreSQL-compatible edition of Amazon Aurora) that includes instances in at least two availability zones.
• A “Service Credit” is a Renminbi credit, calculated as set forth above, that we may credit back to an eligible account.
  
• “Unavailable” and “Unavailability” mean that all connection requests to the running Multi-AZ Cluster fail during a 1 minute interval.