Support for this service has entered open beta.

Added

Virtual Private Cloud (VPC) support for a Managed Database

To enhance security and performance of a Managed Database cluster, you can now assign a VPC to it. You can do this using the new private_network object when creating a new Managed Database, or updating an existing one:

• Create or restore a MySQL Managed Database (POST /databases/mysql/instances)
• Update a MySQL Managed Database (PUT /databases/mysql/instances/{instance_id})
• Create or restore a PostgreSQL Managed Database (POST /databases/postgresql/instances)
• Update a PostgreSQL Managed Database (PUT /databases/postgresql/instances/{instance_id})

📘

• Use of the new private_network object is in beta. We've thoroughly tested it, but it may cause disruptions in certain production environments. We recommend that your thoroughly test it yourself, before putting it in place in your production environment.
• The VPC needs to exist in the same region as the Managed Database cluster.

Support for Premium Linodes

You can now house your Managed Database on a premium plan Linode.

• When creating a new Managed Database (MySQL / PostgreSQL), target a specific premium plan Linode (via the type object).
• When listing Managed Database types, a Managed Database running on a premium Linode shows its type as premium.

Changed

• List Managed Databases (GET /databases/instances). Updates to the hosts object when returned for this operation. Specifically, this includes requirements for the use of these hostnames when incorporating a VPC for the Managed Database.

Fixed

• Open a support ticket (POST /support/tickets). Addressed the availability of the severity object for some accounts.