Cloud Infrastructure Clause Samples

The Cloud Infrastructure clause defines the responsibilities and requirements related to the use and management of cloud-based computing resources within an agreement. It typically outlines which party provides the infrastructure, the standards for security and data protection, and any limitations on usage or access. For example, it may specify that data must be stored in certain geographic regions or that the provider must maintain specific uptime levels. This clause ensures that both parties understand their obligations regarding cloud services, helping to allocate risk and maintain service reliability.
POPULAR SAMPLE Copied 2 times
Cloud Infrastructure. Under our “Cloud Infrastructure” offering, we will procure certain cloud infrastructure service offerings on your behalf from our third-party service provider (either Amazon Web Services or Microsoft Azure, as applicable) to host the MicroStrategy Cloud Platform in a MicroStrategy Cloud Environment, as further described in the MCE Service Guide; those infrastructure service offerings will be operated out of a data center location or region specified on an order or that you and we otherwise mutually determine. Each MCE Service order will list the minimum amount you will pay us during the MCE Service Term for the cloud infrastructure service offerings based on your anticipated infrastructure needs, which will reflect the fees that we anticipate we will incur from our Third-Party Solution infrastructure provider (either Amazon Web Services or Microsoft Azure, as applicable) for those offerings plus twenty percent (20%). Following the execution of an order, you may request in writing (including by email) that we procure additional cloud infrastructure service offerings during the MCE Service Term and we will procure those on your behalf. We will invoice you periodically for any additional fees that we incur from our Third-Party Solution infrastructure provider arising from your use of the MCE Service, including for those additional offerings, plus twenty percent (20%).
View SourceView Similar (6)
Cloud Infrastructure. The PARTHENOS e-infrastructure architecture consists of a hardware layer and a service layer. The hardware layer is organized as a dynamic pool of virtual machines, supporting computation and storage. The operations and management of those resources is performed via a set of enabling technologies selected to ensure availability and reliability of the infrastructure while guaranteeing reduction of costs of ownership and a set of supporting technologies selected to ensure secure monitoring, alerting and provisioning. The services layer is organized into layered software frameworks that increasingly hide the complexity of the cloud-based infrastructure.
View SourceView Similar (3)
Cloud Infrastructure. PortX uses the Amazon Web Service (“AWS”), Microsoft Azure (“Azure”) for cloud infrastructure for its Hosted Solution. To the extent that PortX uses AWS, End Customer acknowledges the use of the Hosted Solution is subject to the terms and limitations set forth in the AWS End Customer Agreement: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇/com/agreement/. To the extent that PortX utilizes Azure for its Hosted Solution. End Customer acknowledges the use of the Hosted Solution is subject to the terms and limitations set forth in the Microsoft Azure Service Agreement: ▇▇▇▇▇://▇▇▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/en-us/support/legal/
View Source
Cloud Infrastructure. ○ Cloud-based hosting for scalability, reliability, and high availability. ○ Secure storage and processing of data, ensuring compliance with PII and HIPAA regulations.
View Source

Related to Cloud Infrastructure

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at ▇▇▇▇▇’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.