In this case, we must multiply the availability target of each service. The following image shows an example of a typical web application that runs on EC2. For EC2 (and related services), the following credits are available: Typically, each SLA covers a service provided in multiple Availability Zones within the same region. In this article, we look at SLAs for some of the most widely used AWS services, including EC2, RDS, EBS, ECS, Fargate, and S3, to give you an idea of what`s on offer, but it`s just a guide and shouldn`t be considered a substitute for reading the actual ISS for the services you want to use. The service credits for S3 Intelligent-Tiering, S3 Infrequent Access standard and S3 One Zone-Infrequent Access are as follows: The examples presented show an expected availability of 99.80% to 99.92% depending on the services involved. This Amazon Service Agreement (this “SLA”) is a policy that governs the use of the included services (see below) and applies separately to each account using the Included Services. In the event of any conflict between the terms of this SLA and the terms of the AWS Customer Agreement or any other agreement with us that governs your use of our services (the “Agreement”), the terms of this SLA apply, but only to the extent of such conflict. The wholesale terms used there, but not defined here, have the meaning defined in the agreement. So here you have some important things to keep in mind and keep in mind when trying to understand Amazon service agreements.
The most important advice I would give is not to rely on service level agreements to ensure the availability of your applications. The SLA provides some instructions on the hours of operation you can expect, but the service credits offered, provided you`re thinking about using them, probably won`t help delay your application downtime and the likely business consequences in terms of lost productivity or perhaps even lost revenue. Amazon EC2`s Service Level Agreement includes several compute services, including: It`s also important to make sure you have good observability of your application infrastructure – if you don`t recognize service outages, you can`t make claims against the SLA and you risk running out of credits. You need to be able to back up your claims with log files – so make sure you know where to get them! All S3 services have a guaranteed availability of 99.9%, with the exception of the following services, which are guaranteed for 99% availability: AWS Support Response times are separate from individual service SLAs. Response time varies between the 3 available AWS support plans – Developer, Business, and Enterprise. To simplify the comparison, I`ve listed the available response times and related support costs in the table below. Don`t expect a 15-minute support response if you`re only paying for a business support plan! Although, in my experience, aws-support is both fast and efficient. The availability SLA varies by S3 service type and the guaranteed operating time is between 99.9% and 99%. . . . .