Amazon IoT Core Service Level Agreement for Amazon Web Services (Ningxia Region)

This Amazon IoT Core Service Level Agreement for Amazon Web Services (Ningxia Region) (“SLA”) is a policy governing the use of Amazon IoT Core 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 agreements 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 IoT Core. 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 Amazon IoT Core available with a Monthly Uptime Percentage for the Amazon Web Services China (Ningxia) region, during any monthly billing cycle, of at least 99.9% (the “Service Commitment”). In the event Amazon IoT Core 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 IoT Core 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 total charges paid by you for Amazon IoT Core in the Amazon Web Services China (Ningxia) region for the monthly billing cycle in which the Monthly Uptime Percentage fell within the ranges set forth in the table below:

We will apply any Service Credits only against future Amazon IoT Core payments otherwise due from you. At our discretion, we may issue the Service Credits 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. Service Credits 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 IoT Core 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 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:

(i) the words “SLA Credit Request” in the subject line;
(ii) the billing cycle with respect to which you are claiming Service Credits, together with the Monthly Uptime Percentage for the billing cycle and the specific dates, times, and Availabilities for each 5-minute interval with less than 100% Availability in the Amazon Web Services China (Ningxia) region throughout the billing cycle;
(iii) your Request logs that document the errors for 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 Credits 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 Service Credits.

Amazon IoT Core SLA Exclusions

The Service Commitment does not apply to any unavailability, suspension or termination of Amazon IoT Core, or any other Amazon IoT Core 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 IoT Core; (ii) that result from any voluntary actions or inactions from you or any third party (e.g. scaling of provisioned capacity, misconfiguring security groups, VPC configurations or credential settings, disabling certificates or making the certificates inaccessible, etc.); (iii) that result from capacity or availability issues of systems in the control of you or any third-party (e.g. insufficient capacity for rules engine action targets, device message queues, etc.); (iv) that result from you not following the best practices described in the Amazon IoT Core Developer Guide on the Amazon Web Services China Site; (v) 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); (vi) that result from exceeding the published Amazon IoT Core service limits as set forth in the Documentation on the Amazon Web Services China Site; or (vii) arising from our suspension or termination of your right to use Amazon IoT Core in accordance with the Agreement (collectively, the “Amazon IoT Core 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

• “Availability” is calculated for each 5-minute interval as the percentage of Requests processed by Amazon IoT Core that do not fail with Errors. If you did not make any Requests in a given 5-minute interval, that interval is assumed to be 100% available.
• An “Error” is:
  • any HTTP API Request that returns a 500 or 503 error code;
  • a device fails to connect to Amazon IoT Core using best practices for retry and exponential back-off;
  • a MQTT Publish Message inbound (from client to service) is Published as QoS1 ("At least once") and the service does not acknowledge (PUBACK) it;
  • a MQTT Publish Message inbound (from client to service) the topic of which is subscribed to by a rule does not trigger the rule; or
  • a MQTT Publish Message outbound (from service to client) has not been delivered to a permanently connected client, successfully subscribed to the message’s topic, within one hour of a Request (such Request and Error are deemed to have both occurred in the five minute interval immediately following the one hour window)
• “Monthly Uptime Percentage” is calculated as the average of the Availability for all 5-minute intervals in a monthly billing cycle. Monthly Uptime Percentage measurements exclude downtime resulting directly or indirectly from any Amazon IoT Core SLA Exclusion.
• “Request” is an invocation of an IoT HTTP API or the sending or receiving of a message over MQTT or Websockets.
• A “Service Credit” is a Renminbi credit, calculated as set forth above, that we may credit back to an eligible account.