Service Certificate – STACKIT Elasticsearch
Service Name
STACKIT Elasticsearch
High level service description
The STACKIT Elasticsearch Service (“Elasticsearch”) provides fully managed instances of Elasticsearch. Elasticsearch is a distributed RESTful search and analytics engine that covers a wide range of document and full-text search-based use cases. As the core of the Elastic Stack, Elasticsearch enables users to search, index, and analyze data of all types and sizes. With Elasticsearch, customers can provision instances of various sizes and use them in applications. Elasticsearch instances are deployed on dedicated virtual machines to ensure isolation and high performance. Customers can choose between replica plans that offer resilient operation with a low level of downtime for use in productive environments and single instances, which we do not recommend for use in productive environments. The customer can meet increasing demand by upgrading to larger instances (service plans). Smoke tests, service guards, and automated backups via Backup Manager ensure the secure operation of Elasticsearch as well as the stored data.
Key Features
- Store, search, index, and analyze data of various natures by leveraging the Elasticsearch engine
- On-demand provisioning: Easy and fast provisioning of new service instances of different sizes
- Service Instance Insulation: Deployment on dedicated virtual machines (Bad Neighborhood Protection)
- Easy capacity upgrades via service plan upgrades
- High availability: Possibility of using replicas for increased resilience and fail-safety
- Logging and monitoring: Communication of logging and monitoring information to defined end points
- Backup: Automatic creation and restoration of backups over a period of up to 14 days
Service Plans
Service Plan | High availability | Number of nodes | vCPU per node | RAM (GB) per node | Disk per node |
---|---|---|---|---|---|
Elasticsearch-1.2.10-Replica | yes | 3 | 1 | 2 | 10 |
Elasticsearch-1.4.10-Replica | yes | 3 | 1 | 4 | 10 |
Elasticsearch-1.4.50-Replica | yes | 3 | 1 | 4 | 50 |
Elasticsearch-2.4.10-Replica | yes | 3 | 2 | 4 | 10 |
Elasticsearch-2.4.50-Replica | yes | 3 | 2 | 4 | 50 |
Elasticsearch-2.8.10-Replica | yes | 3 | 2 | 8 | 10 |
Elasticsearch-2.8.50-Replica | yes | 3 | 2 | 8 | 50 |
Elasticsearch-2.8.100-Replica | yes | 3 | 2 | 8 | 100 |
Elasticsearch-2.8.250-Replica | yes | 3 | 2 | 8 | 250 |
Elasticsearch-4.8.10-Replica | yes | 3 | 4 | 8 | 10 |
Elasticsearch-4.8.50-Replica | yes | 3 | 4 | 8 | 50 |
Elasticsearch-4.8.100-Replica | yes | 3 | 4 | 8 | 100 |
Elasticsearch-4.8.250-Replica | yes | 3 | 4 | 8 | 250 |
Elasticsearch-4.16.50-Replica | yes | 3 | 4 | 16 | 50 |
Elasticsearch-4.16.100- Replica | yes | 3 | 4 | 16 | 100 |
Elasticsearch-4.16.250- Replica | yes | 3 | 4 | 16 | 250 |
Elasticsearch-4.16.500- Replica | yes | 3 | 4 | 16 | 500 |
Elasticsearch-8.16.50-Replica | yes | 3 | 8 | 16 | 50 |
Elasticsearch-8.16.100- Replica | yes | 3 | 8 | 16 | 100 |
Elasticsearch-8.16.250- Replica | yes | 3 | 8 | 16 | 250 |
Elasticsearch-8.16.500- Replica | yes | 3 | 8 | 16 | 500 |
Elasticsearch-8.32.100- Replica | yes | 3 | 8 | 32 | 100 |
Elasticsearch-8.32.250- Replica | yes | 3 | 8 | 32 | 250 |
Elasticsearch-8.32.500- Replica | yes | 3 | 8 | 32 | 500 |
Elasticsearch-8.32.1000- Replica | yes | 3 | 8 | 32 | 1000 |
Elasticsearch-16.32.100- Replica | yes | 3 | 16 | 32 | 100 |
Elasticsearch-16.32.250- Replica | yes | 3 | 16 | 32 | 250 |
Elasticsearch-16.32.500- Replica | yes | 3 | 16 | 32 | 500 |
Elasticsearch-16.32.1000- Replica | yes | 3 | 16 | 32 | 1000 |
Elasticsearch-16.64.500- Replica | yes | 3 | 16 | 64 | 500 |
Elasticsearch-16.64.1000- Replica | yes | 3 | 16 | 64 | 1000 |
Elasticsearch-1.4.10-Single | no | 1 | 1 | 4 | 10 |
Elasticsearch-2.4.10-Single | no | 1 | 2 | 4 | 10 |
Elasticsearch-2.8.50-Single | no | 1 | 2 | 8 | 50 |
Elasticsearch-4.8.50-Single | no | 1 | 4 | 8 | 50 |
Small Cluster | yes | 3 | 2 | 4 | 10 |
Medium Cluster | yes | 3 | 2 | 8 | 50 |
Big Cluster | yes | 3 | 4 | 16 | 100 |
Small Single Instanz | no | 1 | 2 | 4 | 10 |
Medium Single Instance | no | 1 | 2 | 8 | 50 |
Metric
- Billing per hour or part thereof per commissioned Elasticsearch instance.
SLA Specifics
- A booked Elasticsearch instance is considered available if it can be accessed at the service delivery point.
- The provisions of the STACKIT Cloud general service description apply to the availability of Elasticsearch instances.
- To achieve the highest possible availability of Elasticsearch instances (for example, for use in production environments), the use of replicas (3 nodes) is highly recommended.
- When using Elasticsearch with Single Instance Service Plans, a (temporary) unavailability of Elasticsearch instances may occur, especially during maintenance work (e.g. updates), which STACKIT performs on the underlying platform as well as on the selected Service Plans. Maintenance work is considered an excluded event within the meaning of section 2.4 of the STACKIT Cloud service description and is therefore not considered as downtime in the context of availability. The use of Elasticsearch with Single Instance Service Plans in production environments is strongly discouraged.
- Incorrect use of the STACKIT Cloud Portal by the customer with regard to the settings made in self-service and a resulting unavailability of Elasticsearch will not be taken into account with regard to the actually achieved availability of Elasticsearch. The customer is advised that the instance and the associated data may be lost if Elasticsearch is set up and used incorrectly.
Backup
- Instances of Elasticsearch are backed up automatically according to a schedule specified by STACKIT in line with the STACKIT Cloud general service description. This schedule cannot be changed by the customer. However, customers have the ability to create manual backups through the service dashboard and to restore automatic and manual backups.
Additional Terms
- Creating manual backups, as well as restoring backups of Elasticsearch instances, is the responsibility of the customer.