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

This Amazon ElastiCache Service Level Agreement for Amazon Web Services (Ningxia Region) (“SLA”) is a policy governing the use of Amazon ElastiCache (“ElastiCache”) 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 ElastiCache. 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.

SLAs

We make four SLA commitments for ElastiCache: (1) a Multi-AZ ElastiCache SLA and, (2) a Cross-AZ ElastiCache SLA, (3) a Previous Generation Multi-AZ ElastiCache SLA, and (4) a Single-AZ ElastiCache SLA.

Multi-AZ ElastiCache SLA

We will use commercially reasonable efforts to make each ElastiCache for Redis Multi-AZ Configuration available with a Monthly Uptime Percentage as shown in the table below during any monthly billing cycle (the “Multi-AZ ElastiCache SLA”). 

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%	25%
Less than 95.0%	100%

Cross-AZ ElastiCache SLA and Previous Generation Multi-AZ ElastiCache SLA

We will use commercially reasonable efforts to make each ElastiCache for Memcached Cross-AZ Configuration and ElastiCache for Redis Previous Generation Multi-AZ Configuration available with a Cross-AZ and Previous Generation Multi-AZ Uptime Percentage, as applicable, as shown in the table below during any monthly billing cycle (each, as applicable, the "Cross-AZ ElastiCache SLA” and/or “Previous Generation Multi-AZ ElastiCache SLA").

Cross-AZ and Previous Generation Multi-AZ 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.0%	100%

Single-AZ ElastiCache SLA

For each individual ElastiCache for Memcached Single-AZ Configuration and each individual ElastiCache for Redis Single-AZ Configuration, we will use commercially reasonable efforts to make the applicable ElastiCache for Memcached or ElastiCache for Redis Single-AZ Configuration available with a Single-AZ Uptime Percentage as shown in the table below during any monthly billing cycle (the "Single-AZ ElastiCache SLA").  

Single-AZ 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.0%	100%

Service Credits

Service Credits are calculated as a percentage of the total charges paid by you for the ElastiCache for Redis Multi-AZ Configuration, ElastiCache for Memcached Cross-AZ Configuration, ElastiCache for Redis Previous Generation Multi-AZ Configuration, ElastiCache for Memcached Single-AZ Configuration, or ElastiCache for Redis Single-AZ Configuration, as applicable, in Amazon Web Services China (Ningxia) region for the monthly billing cycle in which the SLA, as applicable, was not met. The Service Credits provided to you under this SLA will be provided to you only in connection with your use of ElastiCache from Amazon Web Services China (Ningxia) region. This SLA does not authorize you to receive any Service Credit from any other Amazon Web Services regions.

We will apply any Service Credits only against future ElastiCache 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 ElastiCache 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 Amazon Web Services Support Center. You may not combine or stack claims under the Multi-AZ ElastiCache SLA, Cross-AZ ElastiCache SLA, Previous Generation Multi-AZ ElastiCache SLA, and/or the Single-AZ ElastiCache SLA for a particular ElastiCache 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-AZ, Cross-AZ, Previous Generation Multi-AZ, or Single-AZ ElastiCache SLA, as applicable:

i. the words “ElastiCache SLA Credit Request” in the subject line;

ii. the dates and times of each Unavailability incident you are claiming;

iii. the Shard Names (if applicable), the Cluster Names, and the Amazon Web Services region of the affected ElastiCache for Redis Multi-AZ Configurations, ElastiCache for Memcached Cross-AZ Configurations, ElastiCache for Redis Previous Generation Multi-AZ Configurations, or ElastiCache Single-AZ Configurations; 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 request occurred. Your failure to provide the requested and other information as required above will disqualify you from receiving a Service Credit.

Amazon ElastiCache for Memcached SLA Exclusions

The respective SLAs do not apply to any unavailability, suspension or termination of ElastiCache, or any other ElastiCache 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 ElastiCache; (ii) that result from any voluntary actions or inactions from you; (iii) that result from you not following the recommended caching strategies and best practices described in the ElastiCache for Memcached Documentation on the Amazon Web Services China Site; (iv) caused by underlying in-memory engine software that leads to repeated engine crashes or an inoperable ElastiCache for Memcached node; (v) that result from your equipment, software or other technology; or (vi) arising from our suspension and termination of your right to use ElastiCache in accordance with the Agreement.

If availability is impacted by factors other than those explicitly used in our Cross-AZ Uptime Percentage or Single-AZ Uptime Percentage calculation, as applicable, then we may issue a Service Credit considering such factors at our discretion.

Amazon ElastiCache for Redis SLA Exclusions

The respective SLAs do not apply to any unavailability, suspension or termination of ElastiCache, or any other ElastiCache 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 ElastiCache; (ii) that result from any voluntary actions or inactions from you; (iii) that result from you not following the recommended caching strategies and best practices described in the ElastiCache for Redis User Guide; (iv) caused by underlying in-memory engine software that leads to repeated engine crashes or an inoperable ElastiCache for Redis node; (v) that result in long recovery time due to insufficient capacity for your in-memory workload; (vi) that result from your equipment, software or other technology; or (vii) arising from our suspension and termination of your right to use ElastiCache in accordance with the Agreement.

If availability is impacted by factors other than those explicitly used in our Monthly Uptime Percentage, Previous Generation Multi-AZ Uptime Percentage, or Single-AZ Uptime Percentage calculation, as applicable, then we may issue a Service Credit considering such factors at our discretion.

Definitions

• “Cross-AZ Configuration” means an ElastiCache for Memcached cluster deployed in at least two separate Availability Zones (AZs) within the Amazon Web Services China (Ningxia) region. 
• “Cross-AZ Uptime Percentage” for a given Cross-AZ Configuration is calculated as: 100% minus the percentage of 1-minute intervals during the monthly billing cycle in which the cluster was “Unavailable”. If you have been running that Cross-AZ Configuration for only part of the month, your Cross-AZ Configuration is assumed to be 100% available for the portion of the month that it was not running. 
• “Monthly Uptime Percentage” for a given Multi-AZ Configuration is calculated as the average across the Multi-AZ Configuration’s shards of the following calculation for each such shard: 100% minus the percentage of 1-minute intervals during the monthly billing cycle in which the shard was “Unavailable”. If you have been running that Multi-AZ Configuration for only part of the month, your Multi-AZ Configuration is assumed to be 100% available for the portion of the month that it was not running. 
• “Multi-AZ Configuration” means an ElastiCache for Redis cluster configured with Redis version 6.2 and above and (a) (i) created on or after January 13, 2023, or (ii) with an engine service update released on or after January 13, 2023 applied, and (b) with the Multi-AZ setting enabled on the cluster.
• “Previous Generation Multi-AZ Configuration” means an ElastiCache for Redis cluster configured with any Redis version and (a) with automatic failover enabled, and (b) with a primary and replica set in each shard deployed in at least two separate Availability Zones (AZs).
• “Previous Generation Multi-AZ Uptime Percentage” for a given Previous Generation Multi-AZ Configuration is calculated as the average across the Previous Generation Multi-AZ Configuration’s shards of the following calculation for each such shard: 100% minus the percentage of 1-minute intervals during the monthly billing cycle in which the shard was "Unavailable". If you have been running that Previous Generation Multi-AZ Configuration for only part of the month, your Previous Generation Multi-AZ Configuration is assumed to be 100% available for the portion of the month that it was not running. 
• A “Service Credit” is a Renminbi credit, calculated as set forth above, that we may credit back to an eligible account.
• “Single-AZ Configuration” means, with respect to ElastiCache for Memcached, a cluster deployed in a single Availability Zone (AZ) within the Amazon Web Services China (Ningxia) region.
• “Single-AZ Configuration” means, with respect to ElastiCache for Redis, a cluster configured (a) with automatic failover not enabled, or (b) without a primary and replica set in each shard deployed in at least two separate Availability Zones (AZs).
• “Single-AZ Uptime Percentage” for a given Single-AZ Configuration is calculated as: 100% minus the percentage of 1-minute intervals during the monthly billing cycle in which the cluster was "Unavailable". If you have been running that Single-AZ Configuration for only part of the month, your Single-AZ Configuration is assumed to be 100% available for the portion of the month that it was not running.
• “Unavailable” or “Unavailability” mean, with respect to an ElastiCache for Memcached cluster running in a Cross-AZ or Single-AZ Configuration, that the cluster has no external connectivity.
• “Unavailable” or “Unavailability” mean, with respect to an ElastiCache for Redis shard running in a Multi-AZ, Previous Generation Multi-AZ, or Single-AZ Configuration, that all connection requests to the primary node of the shard fail during a 1-minute interval.

Prior Version(s)