Abstract
Hybrid Cloud Service Level Agreements (SLA) comprises of the legal terms and conditions for the cloud contract. Even though all the service level objectives, metrics and service descriptions are clearly outlined in the cloud SLA contract, sometimes vendors fail to meet the promised services and confusing terms lead to tenant-vendor cloud legal battles. Hybrid Cloud involves two different cloud models (public and private) working together, applications running under the hybrid cloud are subject to different availability sets, functionality and parameters developing SLA complexity and ambiguity. The new manufacturing environment (Industry 4.0 concept) is based on a fully connected, intelligent and automated factory, which will highly be dependent on cloud computing and IoT-based solutions for data analytics, storage and computational needs. In situations where Hybrid cloud services are not defined and managed properly may result in Industrial-IoT data security issues leading to financial and data losses. This paper discusses various aspects of the cloud service level agreement in Industry 4.0 for better understanding and implementation and puts a light on the issues that arise out of imprecise statements.
Highlights
Cloud Computing is well-known for efficiently providing computational, storage and resource provision services in a multi-tenant environment, saving process and people cost [1]
Cloud vendors state that these issues can be controlled through a Service Level Agreement but majority of the Service Level Agreements (SLA) contracts are improperly defined, ambiguous and end-in vendor lock-in situation, which are discussed in this paper in detail
Cloud Failures: Amazon Web Service (AWS), Azure and Google Compute Platform (GCP) have their own set of limitations and all have undergone outages and failures, and there are so many exclusions mentioned in Vendor SLAs
Summary
Cloud Computing is well-known for efficiently providing computational, storage and resource provision services in a multi-tenant environment, saving process and people cost [1]. Vendors may have pre-defined exclusions to a CSLA, such as: hardware, software, network or monitoring failure, scheduled downtime, Denial of Service (DoS), force majeure, etc These service disruptions may highly impact I4.0 tenants if their hybrid cloud is configured to operate on a single geographic zone and lead to major operational and financial loss. Private cloud applications are on-premises and SLAs managed by organizations themselves, through IT Operational Tools providing insights, visibility and control of the environment. These SLAs become critical when organizations form a hybrid cloud, since some of the applications are moved on a public cloud or run under both public/private simultaneously and are subject to different QoS metrics.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
