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.
- 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.
- Select the type of database you’d like to set up. There are two types of managed databases MedStack can provision:
- Configure the database version, node that powers the service, storage capacity, and credentials to manage the database.
- Click "CREATE" to spin up the database and its node.
The following database types and configurations are supported in MedStack's managed database service.
The following node tiers and storage capacities are supported in MedStack's managed database service.
|Basic||1||2 GB||5 GB to 1 TB||Variable|
|Basic||2||4 GB|| 5 GB to 1 TB
|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
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 email@example.com.
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:
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
When you create a managed database on MedStack, it is automatically configured with an intrusion detection system (IDS) and backups. More information on Azure managed databases for MySQL and PostgreSQL can be found in our Backups section.
Should you need to restore a managed database, please contact us at firstname.lastname@example.org.
Storage auto growth
Azure managed databases support the ability to auto grow storage for single server databases. All managed databases created via MedStack are provisioned to auto grow storage by default.
It is important to note that Basic, General Purpose, and Memory Optimized database servers have different maximum sizes. The latest on these single server storage capacities can be found here.