AWS has issued a Service Level Agreement (SLA) for AWS Systems Manager, which offers availability guarantees for AWS Systems Manager. AWS offers service credits for non-compliance with the ALS operating time, but it is important to note that they are not applied automatically. To obtain service credits for downtime, AWS customers must assert a right to credit by opening a business in the AWS assistance centre with the words “SLA credit requirement” in the subject line and specifying the details of the dates and times of defaults or failures for which you use secure credits with protocols and resource IDs for the services concerned. If service credits are available for loss, they are normally used as credit on future invoices for the same service. For EC2 (and associated services), the credits available are: For all RDS instances hosted in multiple availability areas (the “Multi AZ” setting is set at “True”), Amazon guarantees 99.5% operating time on each monthly billing cycle. This allows up to 3.65 hours of downtime per month. For applications that cannot tolerate downtime, customers should consider hosting their databases in multiple regions or using another database service, such as Amazon Aurora, which has an ALS with a 99.99% operating time. The SLA operating time varies depending on the type of S3 service and the guaranteed operating time varies from 99.9% to 99%. In this article, we look at THE SLAs for some of the most commonly used AWS services, including EC2, RDS, EBS, ECS, Fargate and S3, to give you a taste of the offer, but this is only a guide and should not be considered a substitute for reading real SLAs for the services you want to use. All S3 services have a guaranteed operating life of 99.9%, with the exception of the following services, which are guaranteed for 99% of operating time: Service credits for S3 services (except those mentioned above) are: AWS provides all the tools and services needed to implement a strong, highly available and highly secure cloud infrastructure, but it is up to you to ensure that best practices are followed. that you respect the principles of the AWS Well Architected and that you fulfill your responsibilities in the AWS shared responsibility model, so you have a few important things to consider when trying to understand Amazon Web Services service level agreements.
The most important advice I would offer is not to rely on service level agreements to guarantee the operating time of your applications.