Service Certificate – STACKIT Load Balancer
Service Name
STACKIT Load Balancer
High level service description
The STACKIT Load Balancer (“Load Balancer“) provides a compact and integrated load balancer. This enables customers to distribute the load of incoming requests to different STACKIT compute engines (virtual machines) and can thus increase their overall availability.
The provision of the service is ensured in the form of a deployment of two virtual machines (VMs) in the customer project by the STACKIT Load Balancer API, which also takes care of the management of the load balancer instances.
Key Features
- Increase the availability of customer services within the project
- Performance optimization by distributing data traffic to target systems
Service Plans
Plan | Type | vCPU | Memory (GB) | Region |
Essential-Network-Load-Balancer-10-EU01 | High Availability (HA) (Active / Passive) (2 VMs) | 1 | 1 | EU01 |
Essential-Network-Load-Balancer-50-EU01 | High Availability (HA) (Active / Passive) (2 VMs) | 4 | 4 | EU01 |
Essential-Network-Load-Balancer-250-EU01 | High Availability (HA) (Active / Passive) (2 VMs) | 8 | 8 | EU01 |
Essential-Network-Load-Balancer-750-EU01 | High Availability (HA) (Active / Passive) (2 VMs) | 16 | 16 | EU01 |
Metric
- The billing of the STACKIT Load Balancer takes place per managed load balancer per commenced hour until the respective load balancer is deleted
- STACKIT cloud services procured by the customer within the project (e.g. VMs, storage, network) that are required to operate the load balancer are additionally billed separately under the conditions specified in the respective cloud service and are not included in the price of the STACKIT Load Balancer services included
- Der Load Balancer Service setzt sich demnach aus folgenden STACKIT Cloud Services zusammen, die gesondert in Rechnung gestellt werden:
- STACKIT Load Balancer
- Two Compute Engines as active-passive deployment for high availability
- Optional: A public IP if the load balancer is deployed as an external load balancer
- Der Load Balancer Service setzt sich demnach aus folgenden STACKIT Cloud Services zusammen, die gesondert in Rechnung gestellt werden:
- STACKIT Load Balancers are billed per hour or part there of
SLA Specifics
- Availability is defined as the percentage of time that the STACKIT Load Balancer Service is able to distribute traffic
- The availability of the STACKIT Load Balancer Service is linked to the availability of the underlying virtual machines
- Manual intervention by the customer to the virtual machines can have a negative impact on the availability of the STACKIT Load Balancer Service
- The customer is responsible for configuring the STACKIT Load Balancer. Incorrect configurations can lead to reduced availability
Backup
- The customer is responsible for performing load balancer configuration backups and restoring them
- STACKIT bietet dem Kunden die Möglichkeit, über die STACKIT Load Balancer API auf seine aktuelle STACKIT Load Balancer Konfiguration zuzugreifen, siehe hierzu: API DOCS
- The STACKIT Load Balancer Service does not secure any secrets of the customer, for example access data for a STACKIT ARGUS integration to which the customer has subscribed. After a disaster recovery, these must be recreated by the customer
Additional Terms
- The following conditions also apply to the use of the STACKIT Load Balancer Service
Version 1.2, valid from 04.06.2024