Service Certificate – STACKIT OpenSearch
Service Name
STACKIT OpenSearch
High level service description
The STACKIT OpenSearch Service („OpenSearch”) provides fully managed instances of OpenSearch. OpenSearch is a distributed RESTful search and analytics engine that covers a wide range of document and full-text search-based use cases. OpenSearch makes it possible to search, index, and analyze data of any type and amount. With OpenSearch, customers can provision instances of various sizes and use them in applications. OpenSearch 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. Customers 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 OpenSearch as well as the stored data.
Key Features
- Store, search, index, and analyze data of various natures by leveraging the OpenSearch 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
Within the framework of the order, the customer has the option to choose from different service configurations. These mainly differ in their performance capabilities or storage capacity.
| Service Plan | High availability | Number of nodes | vCPU per node | RAM (GB) per node | Disk per node |
|---|---|---|---|---|---|
| OpenSearch-1.2.10-Replica | yes | 3 | 1 | 2 | 10 |
| OpenSearch-1.4.10-Replica | yes | 3 | 1 | 4 | 10 |
| OpenSearch-1.4.50-Replica | yes | 3 | 1 | 4 | 50 |
| OpenSearch-2.4.10-Replica | yes | 3 | 2 | 4 | 10 |
| OpenSearch-2.4.50-Replica | yes | 3 | 2 | 4 | 50 |
| OpenSearch-2.8.10-Replica | yes | 3 | 2 | 8 | 10 |
| OpenSearch-2.8.50-Replica | yes | 3 | 2 | 8 | 50 |
| OpenSearch-2.8.100-Replica | yes | 3 | 2 | 8 | 100 |
| OpenSearch-2.8.250-Replica | yes | 3 | 2 | 8 | 250 |
| OpenSearch-4.8.10-Replica | yes | 3 | 4 | 8 | 10 |
| OpenSearch-4.8.50-Replica | yes | 3 | 4 | 8 | 50 |
| OpenSearch-4.8.100-Replica | yes | 3 | 4 | 8 | 100 |
| OpenSearch-4.8.250-Replica | yes | 3 | 4 | 8 | 250 |
| OpenSearch-4.16.50-Replica | yes | 3 | 4 | 16 | 50 |
| OpenSearch-4.16.100-Replica | yes | 3 | 4 | 16 | 100 |
| OpenSearch-4.16.250-Replica | yes | 3 | 4 | 16 | 250 |
| OpenSearch-4.16.500-Replica | yes | 3 | 4 | 16 | 500 |
| OpenSearch-8.16.50-Replica | yes | 3 | 8 | 16 | 50 |
| OpenSearch-8.16.100-Replica | yes | 3 | 8 | 16 | 100 |
| OpenSearch-8.16.250-Replica | yes | 3 | 8 | 16 | 250 |
| OpenSearch-8.16.500-Replica | yes | 3 | 8 | 16 | 500 |
| OpenSearch-8.32.100-Replica | yes | 3 | 8 | 32 | 100 |
| OpenSearch-8.32.250-Replica | yes | 3 | 8 | 32 | 250 |
| OpenSearch-8.32.500-Replica | yes | 3 | 8 | 32 | 500 |
| OpenSearch-8.32.1000- Replica | yes | 3 | 8 | 32 | 1000 |
| OpenSearch-16.32.100- Replica | yes | 3 | 16 | 32 | 100 |
| OpenSearch-16.32.250- Replica | yes | 3 | 16 | 32 | 250 |
| OpenSearch-16.32.500- Replica | yes | 3 | 16 | 32 | 500 |
| OpenSearch-16.32.1000- Replica | yes | 3 | 16 | 32 | 1000 |
| OpenSearch-16.64.500- Replica | yes | 3 | 16 | 64 | 500 |
| OpenSearch-16.64.1000- Replica | yes | 3 | 16 | 64 | 1000 |
| OpenSearch-1.4.10-Single | no | 1 | 1 | 4 | 10 |
| OpenSearch-2.4.10-Single | no | 1 | 2 | 4 | 10 |
| OpenSearch-2.8.50-Single | no | 1 | 2 | 8 | 50 |
| OpenSearch-4.8.50-Single | no | 1 | 4 | 8 | 50 |
| OpenSearch-4.8.250-replica-HiPerf | yes | 3 | 41 | 8 | 250 |
| OpenSearch-4.16.500-replica-HiPerf | yes | 3 | 41 | 16 | 500 |
| OpenSearch-8.16.500-replica-HiPerf | yes | 3 | 81 | 16 | 500 |
| OpenSearch-8.32.1000-replica-HiPerf | yes | 3 | 81 | 32 | 1000 |
| OpenSearch-16.32.1000-replica-HiPerf | yes | 3 | 161 | 32 | 1000 |
| OpenSearch-16.64.1000-replica-HiPerf | yes | 3 | 161 | 64 | 1000 |
1 dedicated CPU for highest performance
A subsequent downgrade of the service plan initially selected by the customer is not possible.
Metric
- Billing per hour or part thereof per commissioned OpenSearch instance.
SLA Specifics
- A booked OpenSearch 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 OpenSearch instances.
- To achieve the highest possible availability of OpenSearch instances (for example, for use in production environments), the use of replicas (3 nodes) is highly recommended.
- When using OpenSearch with Single Instance Service Plans, a (temporary) unavailability of OpenSearch 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 OpenSearch 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 OpenSearch will not be taken into account with regard to the actually achieved availability of OpenSearch. The customer is advised that incorrect setting and use of OpenSearch may lead to a loss of the instance and the related data.
Backup
- OpenSearch instances are automatically saved according to a schedule stipulated by STACKIT in line with the general service description for STACKIT Cloud. 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 OpenSearch instances, is the responsibility of the customer.
Version 1.2