Amazon Timestream Service Level Agreement

This Amazon Timestream Service Level Agreement ("SLA") is a policy governing the use of Amazon Timestream for Live Analytics and Amazon Timestream for InfluxDB (collectively "Timestream") and applies separately to each account using Timestream. 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.

AWS makes three SLA commitments for Timestream: (1) a Standard SLA for Amazon Timestream for Live Analytics; (2) a Multi-AZ DB Instance SLA for Amazon Timestream for InfluxDB; and (3) a Single-DB Instance SLA for Amazon Timestream for InfluxDB.

AWS will use commercially reasonable efforts to make Amazon Timestream for Live Analytics available with a Monthly Uptime Percentage as shown in the table below during any monthly billing cycle (the “Standard SLA”).

AWS will use commercially reasonable efforts to make Amazon Timestream for InfluxDB available with a Monthly Uptime Percentage as shown in the table below during any monthly billing cycle (the “Multi-AZ DB Instance SLA”).

AWS will use commercially reasonable efforts to make each Single-DB Instance for Amazon Timestream for InfluxDB available with an Instance-Level Uptime Percentage as shown in the table below during any monthly billing cycle (the “Single-DB Instance SLA”).

Service Credits are calculated as a percentage of the charges paid by you for Standard Timestream or the Multi-AZ DB Instance that did not meet the Standard SLA and the Multi-AZ DB Instance SLA, as applicable; or for the Single-DB Instances that did not meet the Single-DB Instance SLA 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 Timestream 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, non-performance, or other failure by us to provide Timestream is the receipt of a Service Credit (if eligible) in accordance with the terms of this SLA.

To receive a Service Credit, you must submit a claim by opening a case in the AWS Support Center. You may not combine or stack claims under the Standard SLA, Multi-AZ DB Instance SLA, and the Single-DB Instance SLA. 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 Standard SLA and Multi-AZ DB Instance SLA, or Single-DB Instance SLA, as applicable :

i. the words "Amazon Timestream SLA Credit Request – Standard/Multi-AZ /Single-DB Claim" in the subject line;

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

iii. the DB Instance IDs and the AWS regions of the affected Standard Instances, Multi-AZ DB Instances, or Single-DB Instances; 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 request and other information as required above will disqualify you from receiving a Service Credit.

The respective SLAs do not apply to any unavailability, suspension, or termination of Timestream or any other Timestream 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 Timestream (ii) that result from any actions or inactions by you; (iii) that result from you not following the guidelines and best practices described in the Timestream Documentation on the AWS Site; (iv) caused by underlying database engine software that lead to repeated database crashes or an inoperable database instance; (v) that result from your equipment, software or other technology; or (vi) arising from our suspension or termination of your right to use Timestream in accordance with the Agreement (collectively, the " Timestream SLA Exclusions").

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

• An "Error" is any Request that returns a 500 or 503 error code, as described in Timestream Common Errors on the AWS Site.

• “Instance-Level Uptime Percentage” for a given Single-DB Instance is calculated by subtracting from 100% the percentage of 5-minute intervals during the monthly billing cycle in which the Single-DB Instance was "Unavailable". If you have been running that Single-DB Instance for only part of the month, your Single-DB Instance is assumed to be 100% available for the portion of the month that it was not running.

• "Monthly Uptime Percentage" for Requests in a given AWS region are calculated by subtracting from 100% the percentage of 5-minute intervals during the monthly billing cycle in which the Requests were Unavailable. If you did not make any Requests in a given 5-minute interval, that interval is assumed to be 100% available. Monthly Uptime Percentage measurements exclude downtime resulting directly or indirectly from any Timestream SLA Exclusions.

• “Multi-AZ Instance” means Amazon Timestream for InfluxDB with the Multi-AZ Instance deployment option selected.

• A "Request" is a customer-initiated action of a type specifically listed as being supported by Timestream in the Timestream API Reference Documentation.

• A "Service Credit" is a dollar credit, calculated as set forth above, that we may credit back to an eligible account.

• “Single-DB Instance” means Amazon Timestream for InfluxDB with the Single-DB deployment option selected.

• “Standard DB Instance” means Amazon Timestream for Live Analytics with the Standard database deployment option selected.

• "Unavailable" and "Unavailability" mean that all Timestream Requests respond with an Error during a 5-minute interval.