Content deleted Content added
Line 87:
Typically, cloud providers' [[Service-level agreement|Service Level Agreements]] (SLAs) do not encompass all forms of service interruptions. Exclusions typically include planned maintenance, downtime resulting from external factors such as network issues, [[Human error|human errors]], like misconfigurations, [[Natural disaster|natural disasters]], [[force majeure]] events, or [[Data breach|security breaches]]. Typically, customers bear the responsibility of monitoring SLA compliance and must file claims for any unmet SLAs within a designated timeframe. Customers should be aware of how deviations from SLAs are calculated, as these parameters may vary by service. These requirements can place a considerable burden on customers. Additionally, SLA percentages and conditions can differ across various services within the same provider, with some services lacking any SLA altogether. In cases of service interruptions due to hardware failures in the cloud provider, the company typically does not offer monetary compensation. Instead, eligible users may receive credits as outlined in the corresponding SLA. <ref>{{Cite book |title=Cloud Security and Privacy An Enterprise Perspective on Risks and Compliance |date=4 September 2009 |publisher=O'Reilly Media |isbn=9781449379513}}</ref><ref>{{Cite book |title=Requirements Engineering for Service and Cloud Computing |date=10 April 2017 |publisher=Springer International Publishing |isbn=9783319513102}}</ref><ref>{{Cite book |last=Srinivasan |title=Cloud Computing Basics |date=14 May 2014 |publisher=Springer |isbn=9781461476993}}</ref><ref>{{Cite book |last=Murugesan |first=San |title=Encyclopedia of Cloud Computing |date=August 2016 |publisher=John Wiley & Sons |isbn=9781118821978}}</ref>
=== Leaky
Cloud computing [[Abstraction (computer science)|abstractions]] aim to simplify resource management, but [[Leaky abstraction|leaky abstractions]] can expose underlying complexities. These variations in abstraction quality depend on the cloud vendor, service and [[Software architecture|architecture]]. Mitigating leaky abstractions requires users to understand the implementation details and limitations of the cloud services they utilize. <ref>{{Cite book |title=Cloud Native Infrastructure: Patterns for Scalable Infrastructure and Applications in a Dynamic Environment |publisher=O'Reilly Media |isbn=9781491984253}}</ref><ref>{{Cite book |title=Cloud Observability in Action |isbn=9781633439597}}</ref><ref>{{Cite book |title=Microservices From Day One: Build robust and scalable software from the start |isbn=9781484219379}}</ref>
=== Service lock-in within the same vendor ===
Service lock-in within the same vendor occurs when a customer becomes dependent on specific services within a cloud vendor, making it challenging to switch to alternative services within the same vendor when their needs change. <ref>{{Cite book |title=Cloud Computing with the Windows Azure Platform |isbn=9781118058756}}</ref><ref>{{Cite book |title=Cloud and Virtual Data Storage Networking |isbn=9781466508446}}</ref>
===Security and privacy===
| |||