Databases


It's incredibly easy to set up clusters and nodes provisioned for healthcare compliance requirements on MedStack Control. With our managed database service, you can now set up MySQL and PostgreSQL databases up to 16 TB in storage capacity with the same ease. This makes hosting and managing stateful applications on MedStack easier and promises a stronger compliance posture across your cloud infrastructure.

Create a managed database service

A managed database can be created in four (4) steps on MedStack Control.

  1. Click the "NEW DATABASE SERVICE" button to start the workflow to set up a new database. This can be found within a cluster in the Control tab.
  2. Select the type of database you’d like to set up. There are two types of managed databases MedStack can provision:
    1. MySQL
    2. PostgreSQL
  3. Configure the database version, node that powers the service, storage capacity, and credentials to manage the database.
  4. Click "CREATE" to spin up the database and its node.

Database configuration

The following database types and configurations are supported in MedStack's managed database service.

Type Supported versions
MySQL 5.6
5.7
8.0
PostgreSQL 9.5
9.6
10.0
11.0

The following node tiers and storage capacities are supported in MedStack's managed database service.

Tier vCPUs Memory Storage capacity IOPS
Basic 1 2 GB 5 GB to 1 TB Variable
Basic 2 4 GB 5 GB to 1 TB
Variable
General Purpose 2 10 GB 5 GB to 16 TB 3 IOPS/GB
Min 100 IOPS
Max 20,000 IOPS
General Purpose 4 20 GB 5 GB to 16 TB 3 IOPS/GB
Min 100 IOPS
Max 20,000 IOPS

Database credentials

In order to safeguard your database, you will need to create database credentials that will be used in your connection strings when accessing the database from other cluster services.

Resetting database credentials

In the event that you need to reset your database credentials, you can do so under the "OPTIONS" dropdown menu for the database service's node.

It is important to note that a username cannot be reset at this time. If you require further assistance with recovering database credentials, please contact support@medstack.co.

Create a database volume

Managed database volumes cannot be created in MedStack’s user interface; however, you can use (1) the credentials established when creating the managed database and (2) a connection string to communicate with a database node to manage volumes.


Obtaining connection strings

In order to communicate with a managed database, you will need to utilize the provided connection strings. The database’s connection strings can be found by clicking the name of the database node.

Currently, connection strings are available for the following development frameworks:

  • ADO.NET
  • JDBC
  • Node.js
  • PHP
  • Python
  • Ruby

In order to successfully establish a connection to the managed database using the connection strings, may will need to update your connection strings with your:

  • Database name
  • User database credentials
  • CA-cert filename

Backup and restore databases

When you create a managed database on MedStack, it is automatically configured to capture snapshots at least once per day and retain data for 35 days.

Should you need to restore a managed database, please contact us at support@medstack.co.


Pricing

It is important to note that manage database services incur costs when running in your MedStack cluster. The following pricing table captures the cost per hour for each tier available in MedStack's managed database service.

Tier vCPUs Memory Storage capacity* Cost (USD)
Basic: 1 core 1 2 GB 5 GB to 1 TB $0.171/hr
Basic: 2 cores 2 4 GB 5 GB to 1 TB $0.205/hr
General Purpose: 2 cores 2 10 GB 5 GB to 16 TB $0.313/hr
General Purpose: 4 cores 4 20 GB 5 GB to 16 TB $0.448/hr

*All database tiers are charged $0.20 USD per GB per month of provisioned storage in addition to the hourly operating costs.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Submit a request for support Submit a request for support