CloudMaster END-USER LICENSE AGREEMENT Version Release Date 2.0 21 October 2021 1 INTRODUCTION 1.1 THE SCOPE OF THE DOCUMENT This End User License Agreement (“EULA”, document) s a legal agreement between End User and Rightholder. If End User use CloudMaster, End User agree to stick to the rules of these EULA. If End User do not want to or can't agree to EULA, then End User shouldn’t use the CloudMaster Software. The document covers the main terms and definitions of services provided by CloudMaster software, as well as licensing, warranties, liabilities and other regulations related to CloudMaster Services usage. End User may not (i) sell, license or distribute copies of the Software or its elements; (ii) grant customers rights to further license or distribute the Software; (iii) license or distribute for commercial purposes logos, trademarks, or emblems or use these types of images in ways that could imply an endorsement or association with End User product, entity or activity. 1.2 DEFINITIONS 1.2.1 Main Definitions Term Definition Software CloudMaster - an AWS-based solution that permits the consolidated viewing and use of cloud infrastructure and management features and reports across the AWS, Google Cloud, and Microsoft Azure third-party cloud environments Service A set of possibilities provided for Service Users within their access to CloudMaster. Rightholder Softline Group Inc, responsible for CloudMaster delivery and support. Service Recipient End User. A legal or private entity, aiming to benefit from using CloudMaster and respective services, or official representatives of such entity. Service User (User) A member of the Service Recipient’s organization, who uses CloudMaster and respective services on behalf of Service Recipient. Support Team A team from Software Rightholder’s side, responsible for CloudMaster maintenance and user support. CloudMaster Account (Account) A logical entity in CloudMaster, created on behalf of the Service Recipient, and used for setting up access to CloudMaster Services. 1.2.2 Software CloudMaster is an AWS-based solution that permits the consolidated viewing and use of cloud infrastructure and management features and reports across the AWS, Google Cloud, and Microsoft Azure third-party cloud environments. The features of the Software include: • Technology features  Self-provisioning  Infrastructure as code  Auto configuration  Hybrid infrastructure  Security inspection • Business features  Governance and access control  Roles and permissions  Unified auditing  Unified billing  Cost control and optimization The Software includes customization features. For example, where applicable, the Software permits users to modify settings such as encryption key storage tenant and region settings, default user permissions, and user interface themes. The Software also permits user permissions management. It facilitates access to native infrastructure tools provided by the Three Cloud Services which can be used separately and which can be customized and complemented with new features provided by the Software. The Software includes a mobile application interface available on devices using iOS and Android operating systems. The mobile application interface includes a notification system whereby the user can create rules for push notifications, email notifications, and custom notifications. 1.3 PARTIES OBLIGATIONS, RESPONSIBILITIES, AND RIGHTS 1.3.1 Shared Responsibility Model The Service follows the industry standard shared responsibility model, with additional layer covered by CloudMaster. The general concept is given on the Figure 1 below: Figure 1 Shared Responsibility Model • Cloud platform providers are responsible for providing their services and enabling security of infrastructures based on their Terms and Conditions, License Agreements, and similar regulations. • CloudMaster takes the basic responsibility for identity and access management, default security configurations, and operating systems selection for default alias mapping. It is also responsible for effective provisioning of all the services included to the offering, according to the respective Account’s settings. • Service Users take the responsibility for Cloud services setup and usage according to respective cloud providers Terms and Conditions, License Agreements, and similar regulations 1.3.2 Rightholder Rightholder is responsible for the following: • Deliver the Software and the respective Services timely and within established SLAs. • Notifying Service Recipient and Service Users about all planned and unplanned service interruptions. • Providing Service Recipient and Service Users with complete and comprehensive information about service delivery status. • Notifying Service Recipient and Users on the changes introduced to the Software and related services. This is done via delivering “What’s New” and “Release Notes” documents, e-mail notifications, or other applicable means. • Notify Service Recipients and Service Users about changes and amendments to the End User Agreement or any other regulatory docs. Rightholder has right to: • Change the Service performance and components. • Stop providing the Service to the Recipients who fail to timely pay for the Service usage. • Stop providing the Service to Service Recipients who fail to keep to local or general legal regulations. 1.3.3 Service Recipient Obligations, Responsibilities, and Rights Service Recipient is obliged to: • Keep to the rules and recommendations covered in this and other Service-related documents. Keep to License and other agreements related to the Public Cloud providers and third-party software used on behalf of the Service Recipient within Service Usage. Service Recipient is responsible for: • Providing the Service Users within their organization with clear instructions on the extent to which they can use the Service, this can include the monthly sum the Recipient agrees to cover for the Service usage. • Timely payment for the Service Usage. Service Recipient has right to: • Request the information on the Service Usage cost, the cost details, and the resources created by Service Users in scope of the Service Recipient’s project needs and get the full details according to the request • Request delivering Cloud education programs to Service users, assigned to Recipient’s organization. Trainings delivery is a paid service. • Cancel the Services usage once necessary, by addressing the Support Team. 1.3.4 Service User Obligations, Responsibilities, and Rights Service User is obliged to: • Keep to the rules and recommendations covered in this and other Service-related documents. Keep to License and other agreements related to the Public Cloud providers and third-party software used within Service Usage. • By request, provide the Service Recipient with the information on the resources the User utilizes in Cloud. Service User is responsible for: • Creating and managing virtual infrastructures within available tenants. • Ensuring timely and effective backup for Service User’s assets. • Ensuring data safety in transit and at rest, according to the Shared Responsibility model. • Timely notifying the Support Team of Software-related issues detected during Services usage.   2 LICENSING OF USE 2.1 MISCELLANEOUS • This agreement is considered accepted by a Service Recipient once an account for Service Recipient’s organization is created, with all related settings negotiated and agreed. • This agreement is considered accepted by a Service User once they login to CloudMaster Dashboard. • By accepting this agreement, Service Users get access to the services, provided by the Software, the extent, defined by Service Recipient during account setup or further customization. • Any Account updates are performed by the Support Team in agreement with and after written approve from an authorized person from the Service Recipient’s side. • The users perform all infrastructure management operations in terms of self-service and according to their permission settings. Users (employees of the Service Recipient) may have limited access to the platform functionality, and such a restriction remains at the discretion and control of the Service Recipient; • Service Users are licensed to use the provided services according to their business needs and within all applicable local and global legal regulations. Rightholder is not liable for any actions performed by Service Users or Service Recipients which violate local or global lows or regulations. • The applications and data managed via the provided Services should comply with all applicable local and global legal regulations. • Service Recipients or Service Users are allowed to use the Services provided by the Software as is. Redistribution, cloning, reverse-engineering, modifying, or altering the Software by Service Recipients or Service Users is strongly prohibited, except the cases when a respective approval for these actions, with defined conditions specified, are provided explicitly by the Rightholder. • The services are provided by the Software in default configuration (including, but not limited to available machine images), checked by security and performance experts from the Rightholder’s side. Service Users are fully responsible for any customizations and user-defined assets (including, but not limited to custom machine images, templates, and keys) and possible results and consequences of their usage. • The Support Team does not perform OS reinstall or updates on existing virtual instances. The recommended way to obtain a new version of an OS is to run a new virtual instance based on a proper image. • Access to the Services is billed according to current Software billing policies. • Rightholder can cancel ay of the provided Services according to the Software change and development plan. The affected Service Recipients and Service Users are informed beforehand. • For effective and correct integration with public Cloud providers, each project, activated in AWS, Azure, or GCP, has a system user account, used by the Software. The system user accounts should not be updated or removed by Service Users or Service Recipients. • The software may be licensed on a trial basis. End User rights to use trial Software are limited to the trial period. • This agreement describes certain legal rights. End User may have other rights under the laws of the relevant country. End User may also have rights with respect to the party from whom End User acquired the Software. This agreement does not change End User’s rights under the laws of the relevant country if the laws of the country do not permit it to do so. 2.2 ACCESS TO SERVICES • The set of services, available for an Account, are discussed with Support Team during Account activation. Later, it can be customized by additional request to Support Team that should be submitted by a responsible person from the Service Recipient side. • The access to Services is provided by domain authorization via Active Directory, or via Google authorization. • A Service User can access and manage only the infrastructure that belongs to the Account to which the user is assigned. • A Service User can access and manage only the infrastructure that belongs to the Tenant to which the user is assigned. • Software functions and Services can be accessed by external users (the users who are not the members of the Service Recipient structure) only in exceptional cases, by request and after specific approval from "approval from responsible Account manager employed by Rightholder. • A service account can be created by request to the Support Team to facilitate CI/CD processes on the project. A Service account can access CloudMaster SDK. • The set of available services and included options can be updated within Software and services capacities by a respective request from authorized persons from Service Recipient side to the Support Team. 2.3 USER PERMISSIONS • Service Users have access to Services within their permissions settings. • Service User permission settings are defined for each available tenant and rely by default on the Service User’s position on each tenant. • The default permission settings are defined at Account creation with accordance to Service Recipient’s business needs. • Personal permissions for each user or group of users can be customized in terms of self-service by authorized users from the Service Recipient’s side. In case self-service customization cannot be performed, the changes can be made by the Support team. • The liability for any consequences of incorrect default permissions settings or default permissions customization is put to responsible persons from the Service Recipient side. 3 DATA SECURITY AND SAFETY • Service Users bear full in responsibility for saving data stored in virtual infrastructures, controlled by the Software. Environments and virtual resources are not backed up or replicated in any way by means of the Software by default. It is the users’ responsibility to define and implement a backup strategy for environment. • The default network configurations. • The Software provides automatic security checks for the virtual infrastructures under its control. The security check results are shared with the Service Users and Support Team via emails and notifications. Fixing the security issues and vulnerabilities described in the emails and notifications is the responsibility of the Service Users. 4 CLOUDMASTER E-MAILS AND NOTIFICATIONS • The Software and Software Support Teams deliver notifications in order to assure sufficient informational support on the events, changes and issues (including security) related to the Software, its services and infrastructures under Software control. • Each notification is addressed to the users who can be influenced by the action, event, or issue described in the message, or to whom the provided information is considered to be important. • The user can unsubscribe from notifications or set up filtering rules in their email client. In this case, the user is responsible for any consequences that result from the delivered information loss. 5 PAYMENTS • The Software automatically calculates account and tenant bills for Services usage based on the billing policies of the public cloud providers used within specific accounts. • All payments for service usage should be performed timely. • Final bills may also include additional payments for Services provisioning within CloudMaster. 6 TERMINATION OF USE • Service usage termination means termination of the Service Recipient’s account in CloudMaster, and all assets stored on CloudMaster side. The resources and services hosted in public cloud providers are not affected, and can be reached via respective public cloud providers native tools. • Service usage can be terminated for an Account by the Rightholder with prior notification in case of the following: • Service usage bills are not paid timely. • Service Recipient or Service Users violate the current agreement or any other Service or Software-related agreements. • Service usage includes breaking local or global legal regulations or laws. • Service usage can be terminated for an Account by request from an authorized person from the Service Recipient side, once there is no further need in the Service. Before service is terminated by request, all service bills should be paid. 7 LIMITATION OF LIABILITY • Rightholder, its employees, affiliates, partners, licensors or suppliers shall not be liable for any damage, unwanted or unexpected consequences resulting from CloudMaster and respective services usage, default configuration customization, data transfer and storage, third-party software or other resources usage within CloudMaster services offering. 8 LIMITED WARRANTY • CloudMaster and related Services are provided “as is”. Rightholder can alter the Software or Services according to the development plan or business conditions, even if the applied changes affect end users. • CloudMaster performance is based on a set of AWS services. Rightholder is not responsible for the used AWS services performance, so under no circumstances should be liable for any CloudMaster performance issues, caused by these services malfunctioning or unexpected changes. • CloudMaster and related Services provide access to third-party tools and public cloud providers, while have no affect on their performance. Under no circumstances should Rightholder be liable for third-party tools and public cloud providers performance or any related errors and their consequences. • Rightholder is not responsible for the performance or any consequences related to misfunction of any supporting services and products, including, but not limited to, network, Service Recipient’s corporate AD, email services, etc.