Service Certificate – STACKIT PostgreSQL
Service Name
STACKIT PostgreSQL
High level service description
The STACKIT PostgreSQL service (“PostgreSQL”) provides fully managed instances of the object-relational database management system (DBMS) PostgreSQL. Customers can provision instances of PostgreSQL in various sizes and use them in applications. The instances of PostgreSQL are deployed on dedicated virtual machines to ensure isolation and high performance. The customer can choose between replica plans, which offer resilient operation with low downtimes for use in productive environments, and single instances, which are not recommended for use in productive environments.). The customer can meet an increasing demand through in-place upgrades to larger instances (service plans). Smoke tests, service guards and the option of automated backups using the Backup Manager ensure the secure operation of the service instances of PostgreSQL as well as the stored data.
Key Features
- 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
Der Kunde hat die Möglichkeit im Rahmen der Bestellung aus verschiedenen Konfigurationen des Service auszuwählen. Diese unterscheiden sich vornehmlich in ihrer Leistungsfähigkeit bzw. Speicherkapazität
| Service Plan | High availability | Number of nodes | vCPU per node | RAM (GB) per node | Disk (GB) per node |
|---|---|---|---|---|---|
| PostgreSQL-1.2.10-Replica | yes | 3 | 1 | 2 | 10 |
| PostgreSQL-1.4.10-Replica | yes | 3 | 1 | 4 | 10 |
| PostgreSQL-1.4.50-Replica | yes | 3 | 1 | 4 | 50 |
| PostgreSQL-2.4.10-Replica | yes | 3 | 2 | 4 | 10 |
| PostgreSQL-2.4.50-Replica | yes | 3 | 2 | 4 | 50 |
| PostgreSQL-2.8.10-Replica | yes | 3 | 2 | 8 | 10 |
| PostgreSQL-2.8.50-Replica | yes | 3 | 2 | 8 | 50 |
| PostgreSQL-2.8.100-Replica | yes | 3 | 2 | 8 | 100 |
| PostgreSQL-2.8.250-Replica | yes | 3 | 2 | 8 | 250 |
| PostgreSQL-4.8.10-Replica | yes | 3 | 4 | 8 | 10 |
| PostgreSQL-4.8.50-Replica | yes | 3 | 4 | 8 | 50 |
| PostgreSQL-4.8.100-Replica | yes | 3 | 4 | 8 | 100 |
| PostgreSQL-4.8.250-Replica | yes | 3 | 4 | 8 | 250 |
| PostgreSQL-4.16.50-Replica | yes | 3 | 4 | 16 | 50 |
| PostgreSQL-4.16.100-Replica | yes | 3 | 4 | 16 | 100 |
| PostgreSQL-4.16.250-Replica | yes | 3 | 4 | 16 | 250 |
| PostgreSQL-4.16.500-Replica | yes | 3 | 4 | 16 | 500 |
| PostgreSQL-8.16.50-Replica | yes | 3 | 8 | 16 | 50 |
| PostgreSQL-8.16.100-Replica | yes | 3 | 8 | 16 | 100 |
| PostgreSQL-8.16.250-Replica | yes | 3 | 8 | 16 | 250 |
| PostgreSQL-8.16.500-Replica | yes | 3 | 8 | 16 | 500 |
| PostgreSQL-8.32.100-Replica | yes | 3 | 8 | 32 | 100 |
| PostgreSQL-8.32.250-Replica | yes | 3 | 8 | 32 | 250 |
| PostgreSQL-8.32.500-Replica | yes | 3 | 8 | 32 | 500 |
| PostgreSQL-8.32.1000-Replica | yes | 3 | 8 | 32 | 1000 |
| PostgreSQL-16.32.100-Replica | yes | 3 | 16 | 32 | 100 |
| PostgreSQL-16.32.250-Replica | yes | 3 | 16 | 32 | 250 |
| PostgreSQL-16.32.500-Replica | yes | 3 | 16 | 32 | 500 |
| PostgreSQL-16.32.1000-Replica | yes | 3 | 16 | 32 | 1000 |
| PostgreSQL-16.64.500-Replica | yes | 3 | 16 | 64 | 500 |
| PostgreSQL-16.64.1000-Replica | yes | 3 | 16 | 64 | 1000 |
| PostgreSQL-1.4.10-Single | no | 1 | 1 | 4 | 10 |
| PostgreSQL-2.4.10-Single | no | 1 | 2 | 4 | 10 |
| PostgreSQL-2.8.50-Single | no | 1 | 2 | 8 | 50 |
| PostgreSQL-4.8.50-Single | no | 1 | 4 | 8 | 50 |
| PostgreSQL-4.8.250-replica-HiPerf | yes | 3 | 41 | 8 | 250 |
| PostgreSQL-4.16.500-replica-HiPerf | yes | 3 | 41 | 16 | 500 |
| PostgreSQL-8.16.500-replica-HiPerf | yes | 3 | 81 | 16 | 500 |
| PostgreSQL-8.32.1000-replica-HiPerf | yes | 3 | 81 | 32 | 1000 |
| PostgreSQL-16.32.1000-replica-HiPerf | yes | 3 | 161 | 32 | 1000 |
| PostgreSQL-16.64.1000-replica-HiPerf | yes | 3 | 161 | 64 | 1000 |
| stackit-postgresql-cluster-small | yes | 3 | 2 | 4 | 10 |
| stackit-postgresql-cluster-medium | yes | 3 | 2 | 8 | 50 |
| stackit-postgresql-cluster-big | yes | 3 | 4 | 16 | 100 |
| stackit-postgresql-cluster-extralarge | yes | 3 | 16 | 32 | 500 |
| stackit-postgresql-single-small | no | 1 | 2 | 4 | 10 |
| stackit-postgresql-single-medium | no | 1 | 2 | 8 | 50 |
1 dedicated CPU for highest performance
A subsequent downgrade of the service plan initially selected by the customer within the same instance is not possible.
Metric
- Billing per hour or part thereof per commissioned PostgreSQL instance
SLA Specifics
- A booked instance of PostgreSQL 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 PostgreSQL instances.
- To achieve the highest possible availability of PostgreSQL (for example, for use in production environments), the use of replicas (3 nodes) is strongly recommended.
- When using PostgreSQL single-instance service plans, PostgreSQL may become (temporarily) unavailable, especially during maintenance work (e.g., through updates) that 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 PostgreSQL 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 PostgreSQL will not be taken into account with regard to the actually achieved availability of PostgreSQL. The customer is advised that the instance and the associated data may be lost if PostgreSQL is set up and used incorrectly.
Backup
- Instances of PostgreSQL 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 PostgreSQL instances, is the responsibility of the customer.