For applications to S3 Intelligent-Tiering, S3 Standard-Infrequent Access and S3 One Zone-Infrequent Access: . . The service level agreement for Amazon EC2 includes several compute services, including: . . To get a service credit, you must apply by opening an application at the AWS Support Centre. To be justified, the credit application must be received until the end of the second billing cycle after which the incident occurred and must include: Service credits are calculated as a percentage of the total costs you pay (excluding one-time payments such as advance payments for Reserved Instances) for each service included in the relevant AWS region for the monthly billing cycle during which the downtime occurred in accordance with the schedule below. . Amazon S3 also offers a „sustainability” guarantee about which you can read more in my S3 Guide article. .
If availability is affected by factors other than those explicitly used in our calculation of the monthly operating percentage, we may, at our discretion, issue a service credit taking these factors into account. 2. the billing cycle and the AWS region for which you use service credits, as well as the dates and times of each incident of zero uneven error rates you use; There you go. AWS will make reasonable economic efforts to ensure that each instance of Amazon EC2 („single EC2 instance”) has an overtime percentage of at least 90% of the time available to this unique EC2 instance each hour (the „hourly commitment”). In the event that only one EC2 instance does not meet the hourly commitment, you will not be charged for the use of unique EC2 instances. . . . If the percentage of the monthly operating time of such a request is confirmed by us and less than the service obligation, we will issue the service credit to you as part of a billing cycle after the month of confirmation of your request. If you do not provide the above requirement and other information, you will be contradicted by receiving a service credit.
Unless otherwise stated in the Agreement, this ALS defines your exclusive and exclusive remedies as well as AWS`s exclusive and exclusive obligations in the event of unavailability, non-performance or any failure on our part to provide the included services. It`s also important to make sure your application infrastructure is observable – if you don`t recognize service outages, you can`t make claims against the ALA, so you can no longer get credits. You need to be able to back up your rights with log files, so make sure you know where to get them! . . Duty of service and duty do not apply to unavailability, suspension or termination of an integrated service or other problems related to service delivery included: (i) caused by factors that are not subject to our proper control, including force majeure events or Internet access or related problems that go beyond the point of demarcation of the service included; (ii) resulting from actions or inactions by you or others, including the non-recognition of a recovery volume; (iii) resulting from your equipment, software or other technology, software or other third-party technology (other than third-party devices from our direct control); or (iv) due to our suspension or termination of your right to use the service included in accordance with the agreement (together the „Amazon Compute SLA exclusions”). If availability is influenced by factors other than the factors used in our calculation of the monthly operating percentage, we may, at our discretion, issue a service credit taking these factors into account.